Expand hardcoded secret detection using open-source references
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Context
From Vincent's review on PR #14 — the current hardcoded secret rules cover AWS, GitHub PAT, and Stripe live keys. There are many more secret formats worth detecting.
Reference projects to pull patterns from
- TruffleHog: https://github.com/trufflesecurity/trufflehog/tree/main/pkg/detectors
- detect-secrets (Yelp): https://github.com/Yelp/detect-secrets/tree/master/detect_secrets/plugins
- Secret Parker (Praetorian): https://github.com/praetorian-inc/titus/tree/main/pkg/rule/rules
High-value candidates to add next
- Slack tokens (
xoxb-,xoxp-,xoxs-) - Twilio keys (
SK+ 32 hex) - SendGrid keys (
SG.) - Database connection strings (postgres://, mongodb://, mysql://)
- Generic JWT detection
- OpenAI / Anthropic API keys
- Datadog / New Relic API keys
Origin
PR #14 review comment by @gewenyu99
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing AWS, GitHub PAT, and Stripe live-key detection rules, then compare candidate patterns in the TruffleHog, detect-secrets, and Secret Parker detector directories. Prioritize the listed Slack, Twilio, SendGrid, database connection, JWT, OpenAI, Anthropic, Datadog, and New Relic formats. Done means the selected additional formats are detected and covered by appropriate verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100