Skip to content

Security: TPEOficial/sprint

Security

SECURITY.md

Security Policy

🛡 Supported Versions

Sprint is under active development and considered [EXPERIMENTAL].
Security updates will be prioritized for the latest version only.

Version Supported
Latest ✅ Yes
Older ❌ No

🚨 Reporting a Vulnerability

If you discover a security vulnerability in Sprint, please report it responsibly.

Do NOT:

  • Open a public GitHub issue for security vulnerabilities.
  • Share exploit details publicly before a fix is available.

Do:

  • Report the issue privately.
  • Provide as much detail as possible:
    • Description of the vulnerability
    • Steps to reproduce
    • Potential impact
    • Suggested fix (if any)

📩 How to Report

Please report security issues via:

  • GitHub Security Advisories (recommended)
  • Or contact the maintainers privately through the project’s official channels.

If applicable, you may also use the project’s official communication channels listed in the repository.


🔒 Security Principles in Sprint

Sprint is designed with the following principles:

  • Minimal attack surface by default
  • Secure headers enabled automatically
  • x-powered-by disabled
  • CORS configurable
  • Rate limiting support
  • Environment-based configuration
  • Explicit route structure
  • No hidden magic behavior

🧪 Experimental Status

Sprint is currently experimental.

Breaking changes may occur until the first stable release.
Security improvements may be introduced frequently.


🙏 Responsible Disclosure

We appreciate responsible disclosure.
Security contributors may be acknowledged publicly if desired.

Thank you for helping keep Sprint secure.

There aren’t any published security advisories