Skip to content

Security: edwardlthompson/DevPulse

SECURITY.md

Security Policy

Supported Versions

Supported template version: see .template-version on main. Security fixes apply to the latest Release Please tag.

Version Supported
latest
< latest

Threat Model

See docs/THREAT_MODEL.md and docs/PRIVACY.md for data-boundary expectations.

Reporting a Vulnerability

Do not open public GitHub issues for security vulnerabilities.

  1. Use GitHub Private vulnerability reporting (Security → Advisories → Report a vulnerability), or
  2. Email the maintainers listed in CODEOWNERS with:
    • Description of the vulnerability
    • Steps to reproduce
    • Impact assessment
    • Suggested fix (if any)

Response Timeline

Stage Target
Acknowledgment 3 business days
Initial assessment 7 business days
Fix or mitigation plan 30 days (severity-dependent)
Public disclosure Coordinated with reporter

Security Practices

  • Dependabot alerts and weekly CVE triage: see docs/SECURITY_TRIAGE.md
  • Maintainer orchestrator: bash scripts/run-maintainer-gates.sh (weekly; full cycle omits --quick)
  • Secrets must never be committed (Gitleaks pre-commit enforced)
  • Report dependency vulnerabilities via Dependabot; do not commit patched forks without review

There aren't any published security advisories