Featured · Technical Systems & AI
Build · Software project
Coverage sample
Sample data
Swipe sideways to explore the table.
| Source | AWS | GitHub | 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 |
Detector Coverage Atlas
Help security practitioners and technical sellers inspect secret-detection coverage and identify what needs review. Explore a small source-backed comparison sample.
How it works
Intended value: What I can claim in discovery, and what I have to leave gray.
Contribution: I built the sample comparing three sources across five credential types and the rule that an unreviewed cell stays gray.
Next.js, React, and TypeScript. The rows live in this repository.
Recorded stage: Software project. Lifecycle: Build.
The comparison is the table on the case study. A later parser is described there and is not part of this page.