Security policy
Report vulnerabilities privately.
Please do not open a public issue. GitHub’s private reporting opens a draft advisory only you and the maintainer can read, so a fix can ship before the details are public.
If private reporting is unavailable to you, email hoangluongtran0309@gmail.com.
What to include
- What you found
- How to reproduce it
- What an attacker could reach
- A proof of concept helps; a working exploit is not required and never needs to be public
After you report
What happens next
ReleaseFlow is a personal project with one maintainer, so there is no paid triage rota and no bounty.
Report privately
Through a private draft advisory on GitHub, or by email.
Whenever you find it
First reply
The maintainer reads the report and answers you.
Within a week
Fix
A report that turns out to be a real weakness is fixed in the latest version and on main.
When the fix is ready
Disclose
The fix, the advisory and the credit go out together.
With the fix
Supported versions
Which versions get fixes
Only the latest released version and the current main. Older versions get no fixes, and with one maintainer there are no backports: please upgrade. The changelog says what each version changed.
| Version | Security fixes |
|---|---|
v1.3.1 Latest release | Supported |
main | Supported |
| Older versions | Not supported |
Security model
How ReleaseFlow protects a deployment
Encrypted credentials
Webhook secrets and access tokens are encrypted with the master key you supply; ReleaseFlow refuses to start without a valid one.
Secrets are write-only
A stored secret is never read back into a page, an API response or a log, and a webhook secret is shown once.
Organizations stay apart
The Organization always comes from the signed-in person, never from a request; another Organization’s data is simply not found.
Signed webhooks, CSRF always on
Each webhook proves itself with its own secret over the raw body. CSRF protection is never turned off; only signed paths are exempt.
Private by default
The quickstart listens on loopback only and never publishes the database; outbound calls go only to what you configure.
Verifiable releases
Each release ships SHA256SUMS, an SBOM and a provenance attestation, and the code is scanned by CodeQL, Dependency Review and a secret scan.
Scope
In scope
The application and its configuration: authentication and session handling, tenant isolation between Organizations, webhook signature verification, secret storage and the reveal-once rules, the outbound clients and their allowlists, and the CSRF and security-header configuration.
Out of scope
- The demo Compose stack (
docker-compose.demo.yml), which exists to evaluate ReleaseFlow locally and is not a production deployment. - A finding that needs an administrator’s own credentials to reach something an administrator may already reach.
- A scanner’s report with no explanation of what it actually reaches.
Running it for a team?
HTTPS, backups and the master key come before your team relies on it.