Shreyas Sriram

## Possible solution I was looking into this and one possible solution is to modify `Verified bool` https://github.com/trufflesecurity/trufflehog/blob/6de778d5108415fba3a582ef26e3ce35fb00d527/pkg/detectors/detectors.go#L29 to a struct. That struct will have two fields; one to know...

Good idea, but how do we filter and print only the ***successfully verified*** requests? From my understanding, it is not good practice to have logic in the custom roundtripper. Otherwise,...

The execution needs to continue onto next iteration if user is not found. Otherwise, execution goes to `sess.addUser(u)` where the segmentation fault is thrown. https://github.com/N0MoreSecr3ts/wraith/blob/5efcf84863d94b5ae9cdfe7a93478df46e211245/core/github.go#L95-L102

Did some digging around this. ## Wraith steps for this scan scenario 1. Clone repo until commit-depth 1 2. Traverse through the commits 3. Get changes (`diff`) from the `parentCommitTree`...

I cannot reproduce this issue locally. `commit-depth` seems to be parsed and overwritten in the correct priority - **_default -> config file -> CLI args_**.

@PrasadG193 Check this out - https://github.com/nikoksr/notify

Revisiting this as part of hacktober. I noticed the `Result` struct has `ExtraData`, which can be used to store the curl validation request (coming out of http2curl). https://github.com/trufflesecurity/trufflehog/blob/6de778d5108415fba3a582ef26e3ce35fb00d527/pkg/detectors/detectors.go#L35 Should be...

+1 to @clonsdale-canva

Would suggest keeping it along with the code for parity.

This appears to be coming from the [Chunker](https://github.com/trufflesecurity/trufflehog/blob/main/pkg/sources/chunker.go) logic. A quick change of `ChunkSize` to `10 * 10 * 1024` returns the correct line number. ``` Found unverified result 🐷🔑❓...