Hardcoded secret candidates
What a hardcoded-secret finding of fallow security means, why it matters and how to fix it.
What it reports
Provider-prefixed or contextual secret literals require verification.
Security explains how fallow finds it.
Why it matters
hardcoded-secret reports opt-in candidates for provider-prefixed or contextual secret-shaped literals. The category is include-required and only runs when listed in security.categories.include. It avoids raw entropy alone, but every result still requires review, secret rotation decisions, and context before acting.
Example
A provider-prefixed token-shaped literal is assigned to a secret-shaped variable, and the hardcoded-secret category is explicitly included.
Fix
Rotate real credentials, move them to a secret manager or environment variable, and keep test-only literals clearly fake so they do not resemble provider tokens.
Facts
| Fact | Value |
|---|---|
| Issue type | hardcoded-secret |
| Rule id in SARIF output | security/hardcoded-secret |
| Command | fallow security |
| Default severity | off |
| Suppression comment | // fallow-ignore-next-line security-sink |
Fixable with fallow fix | No |
| Opt-in | Yes |
Note. Include-required category: enable via security.categories.include.