Security fixes target the latest version on main. This project is a deployed
application, not a published npm package.
Use GitHub's private vulnerability reporting. Do not post exploit details, credentials, or visitor information in a public issue.
Include the affected commit, expected and actual behavior, a minimal reproduction, and the security impact. Use synthetic data or public example addresses; never include real visitor addresses, IPinfo tokens, or Cloudflare credentials.
If a credential has been exposed, revoke or rotate it immediately. Deleting a commit or closing an alert does not invalidate a leaked credential.
CI, CodeQL, dependency review, Dependabot, and Scorecard complement manual review; they do not guarantee that the application is free of vulnerabilities.
Production secrets belong in Cloudflare Worker runtime settings, never in the
repository or GitHub Actions. CI and runtime smoke tests need no production token.
Direct pushes to main remain allowed, so review failed checks and security alerts
before publishing changes. GitHub checks do not gate Cloudflare deployments.
The repository-posture findings below are explicitly accepted recommendations, not fixed application vulnerabilities. Their code-scanning alerts are closed as accepted findings with an individual explanation. Scorecard, CodeQL, dependency review, and all existing checks remain enabled; no queries or results are filtered to conceal these decisions. Full Scorecard results remain available in GitHub.
| Check | Accepted reason | Reassessment |
|---|---|---|
| Branch protection | Direct pushes to main and informative checks are a deliberate project workflow choice. Mandatory PRs or status gates would contradict that choice. |
Revisit if the maintainer changes the workflow policy. |
| Fuzzing | No recognized external fuzzer integration is currently present. Unit and runtime smoke tests exist, but are not claimed to be fuzzing. | Revisit when parsing/input risk or project scope justifies a real fuzzing integration. |
| Code review | Independent approvals are not mandatory, and past changesets have no such approvals. Review history cannot be retroactively fabricated. | Revisit if mandatory independent review becomes part of the project workflow. |
| Maintained | Scorecard flags a repository younger than 90 days. Repository age is not an actionable code defect. | Reassess after the repository is at least 90 days old; do not manufacture activity for a score. |
| OpenSSF Best Practices badge | No badge or certification is currently claimed. Adding an unearned badge would misrepresent the project. | Revisit after actually completing the applicable criteria and registration. |
These decisions do not waive investigation of new application vulnerabilities, dependency advisories, or credential leaks. Reopen an accepted finding if its assumptions change.