Covered
Reviewed for this sample. Only TruffleHog AWS keys and GitHub PATs.
For security practitioners and technical sellers comparing secret-detection coverage, this sample makes the evidence easier to inspect. Compare three sources across five credential types, distinguish reviewed coverage from observations, and see what still needs investigation. My aim is to help people ask better security questions without turning missing evidence into a product claim.
I built this table and the rule that gray is not a gap.
Try the examplePublic-source sample
A source-linked example. Compare the cited evidence and review date for each finding.
Step 1 of 4
Start with the public TruffleHog repository and the sample table below. The table records a limited review, not an exhaustive product evaluation.
Confirmed in the repository that renders this page. Planned tools stay in the case study and are not shown as logos.
02 / The sample
Covered, Observed, and Not evaluated are different claims. The scroll on a narrow screen is the table, not the page.
| Source | AWS keys | GitHub PATs | Slack | GitLab | GCP |
|---|---|---|---|---|---|
| TruffleHog | Covered | Covered | Observed | Observed | Observed |
| Betterleaks | Not evaluated | Not evaluated | Not evaluated | Not evaluated | Not evaluated |
| Kingfisher | Not evaluated | Not evaluated | Not evaluated | Not evaluated | Not evaluated |
Independent research — not an official Truffle product. Covered is only AWS keys and GitHub PATs for TruffleHog. Observed means the public detector folder exists. Gray is not a confirmed gap. The 910 and 14 counts are notes, not rows here.
03 / How to read a cell
Reviewed for this sample. Only TruffleHog AWS keys and GitHub PATs.
A public TruffleHog detector folder exists. Slack, GitLab, and GCP. Verification was not fully reviewed.
No review. Betterleaks and Kingfisher, and any type not in this table.
04 / Open-source attribution and original contribution
Detector Coverage Atlas is my independent research and visualization project. Its detector facts are derived from public TruffleHog source code at pinned revisions; the TruffleHog detector engine and its implementations belong to their upstream project and contributors. This portfolio's comparison is a small static sample, not the full Atlas ingestion application.
The upstream TruffleHog v3 repository identifies AGPL-3.0 as its license. Reading and attributing source is different from copying or modifying covered code. A future fork could explore Go detectors.
05 / How it works
The table reflects a fixed set of reviewed examples, maintained independently from Truffle Security.
Truffle Camp
A secrets-security learning path with a written module and one synthetic practice question.
Try the exampleCompetitive Intelligence Engine
Help sellers turn competitive research into useful buyer conversations. Explore a source-backed field brief and a proposed review workflow.
Try the exampleAccount Intelligence
Help enterprise sellers connect account changes to relevant conversations. Explore a fictional workflow from a signal to a draft, with evidence and assumptions kept separate.
Try the example