DevOps & Cloud · Release risk score
ReleaseScore
Release with eyes open.
A 0 to 100 risk score for every release, each reason behind it, and the precaution to take, learned from your own incidents and test results.
$ release-risk --base HEAD~15
release-risk: MEDIUM (53/100) for HEAD~15..HEAD: 15 commits, 34 files, +1,200/-20 lines
+15 Touches authentication, payments or security code (1 file(s))
+12 Database migration (1 file(s))
Check: Run it on a copy of production data first and time it; check it doesn't lock big tables.
+10 Large change: 894 lines of code in 24 files
+6 Configuration changed
The problem
The release that took the site down was "just a small change". Nobody noticed it dropped a column, touched payment code and had no tests.
What it does
Reads the git history between the last release and now
Learns from your past: files behind earlier reverts, hotfixes and incidents score higher
Reads the release's test run: failing and flaky tests, and coverage of the changed files
History check: which past releases were followed by a revert or hotfix, so you can see the score means something
Destructive database migrations: drops, renames, NOT NULL without default
Authentication, payment, permission and encryption code
Code changed without tests, deleted tests and major dependency upgrades
Infrastructure, CI, configuration and API contract changes
Bug-prone files and authors new to the code
Markdown for the release pull request and a CI gate for the riskiest releases
How it works
- Run it on the release branch or in CI
- Read the score and the reason for each point
- Take the listed precautions, then ship
Works with
Runs in your CI
- uses: actions/checkout@v5
with: { fetch-depth: 0 }
- run: release-risk --base origin/${{ github.base_ref }} --format markdown --out risk.md --fail-above 80
Your data
- Runs locally on the repository.
- Nothing is uploaded.
- Scores are explainable line by line.
Who it's for
Questions
How is it different from BlastRadar?
ReleaseScore scores the release; BlastRadar maps which services it can affect and checks them after deploy. They work well together.
Can it block risky releases?
Yes, as an optional CI gate above a score you choose.
Related
Often used with ReleaseScore
BlastRadar
Change impact analysisKnow what a change will touch. Before a release, see every service a change can affect and the line of code that links it. After the release, confirm those services are still healthy.
$300–600 (₹10,000–20,000 in India)View product → DevOps & CloudSLOStudio
SLOs and error budgetsReliability you can measure. Define each SLO in a few lines and get correct burn-rate alerts, an error budget everyone understands, and a release gate, on the monitoring you already run.
$1,500–3,000 (₹40,000–80,000 in India)View product → DevOps & CloudTestScope
Test impact selectionRun the tests that matter. Every pull request runs the tests its change can affect, each with a stated reason, and the full suite whenever a change is too broad to trust.
$1,000–2,500 (₹25,000–60,000 in India)View product →See ReleaseScore on your own data
A 30-minute call. We run the product on your export, repository or document and walk you through the results.