scout-displacement: evaluate detect-secrets vs custom #166

New issue

Closed

opened 2026-06-04 10:26:02 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-06-04 10:26:02 +00:00

Owner

Candidate OSS to displace secret scanning, surfaced by the scout-displacement run on 2026-06-04.

Tool: https://github.com/Yelp/detect-secrets
Displaces: secret scanning
Fit: low priority - trufflehog already covers this

Before adopting: verify maturity (stars, last release, maintainers, license) and run supply-chain-audit, then settle adopt / partial / keep-custom / watch. Part of the build-vs-buy sweep (tooling-scout-displacement).

Candidate OSS to displace secret scanning, surfaced by the scout-displacement run on 2026-06-04. - **Tool:** https://github.com/Yelp/detect-secrets - **Displaces:** secret scanning - **Fit:** low priority - trufflehog already covers this Before adopting: verify maturity (stars, last release, maintainers, license) and run supply-chain-audit, then settle adopt / partial / keep-custom / watch. Part of the build-vs-buy sweep (tooling-scout-displacement).

coilysiren added the

label

2026-06-17 07:05:25 +00:00

coilysiren commented

2026-06-17 08:23:08 +00:00

Author

Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.

coilysiren

2026-06-17 08:23:08 +00:00