public/security-policy
Public repository has SECURITY.md
| Severity | warning |
| Tiers | 1 |
| Stacks | any |
| Scope | root |
| Kind | expr |
| Source | library v0.4.0 |
| Selected by | fleetlint-recommended@v0.4.0 |
Requirement
A SECURITY file at the root or in .github/, docs/ or .gitea/ explains how to report a vulnerability privately.
Why
Reporters otherwise open public issues, which disclose the problem before a fix exists.
Applies when
repo.publicCheck
exists("SECURITY*") || exists(".github/SECURITY*") || exists("docs/SECURITY*") || exists(".gitea/SECURITY*")Fix
Add SECURITY.md with a private contact and expected response time.
Agent instruction: Add SECURITY.md: supported versions, private reporting channel, response expectation.
fleetlint fix can apply this rule’s fix automatically (1 action(s)).
Sources
- https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository (guidance)
- https://github.com/ossf/scorecard/blob/main/docs/checks.md (standard, Security-Policy)
- https://csrc.nist.gov/pubs/sp/800/218/final (standard, RV.1.3: Have a policy that addresses vulnerability disclosure and remediation)
- https://fleetlint.org/baseline/#public-repositories
Generated by fleetlint docs from catalog v0.4.0.