StackVitals is a free GitHub Action. Every few hours it reads your CI runs, pull requests and releases, keeps the history in a branch of your own repo, and shows what needs a decision. No hosted backend, no account, nothing to host.
Each module keeps its own history and raises its own alerts. Turn on the ones you need.
Flaky and failing tests and jobs from every run, failure groups, the minutes they cost; quarantine, one re-run of known flakes, one issue per flaky test, and a verdict check you can require.
Covers the core workflows of Trunk Flaky Tests, BuildPulse.
Who holds the next move on each pull request, reviews that never started, working agreements your team sets, and a weekly digest.
Covers the core workflows of Swarmia, LinearB.
DORA's five delivery metrics, the first four counted the way Apache DevLake's dashboards count them, and cycle time in LinearB's phases from first commit to production.
Covers the core workflows of Apache DevLake, Sleuth.
Update pull requests by age, security updates past 48 hours, how fast updates merge, and a verdict on each package from public evidence.
Covers the core workflows of Renovate's dashboard, Socket.
Newcomers waiting for a first answer, how fast maintainers answer, stars, and traffic kept past GitHub's 14 days with your own GitHub App.
Covers the core workflows of LFX Insights and the CHAOSS tools.
Every repo in an org with its owners checked, bronze, silver and gold scorecards against peer repos, and campaigns with reminders.
Covers the core workflows of Cortex, OpsLevel, Port.
Your CI runs, pull requests, issues and deployments.
After every CI run and every 3 hours, it reads with the workflow's own token, about a minute a run.
A branch in your repo: every number with its history, every decision with who and why.
A static page on your GitHub Pages, or on your machine for private repos.
Decisions happen where you already work: type /stackvitals quarantine in any issue or pull
request, or press Decide in the app. Every decision is logged with who made it, why and until when.
| What you get | Usually bought from | Their list price |
|---|---|---|
| Flaky tests: detection, quarantine, re-runs, a required check | Trunk Flaky Tests, BuildPulse | Trunk free up to 5 committers; BuildPulse from $99 a month |
| Pull-request flow, review waits, working agreements, weekly digest | Swarmia, LinearB | Swarmia $45 to $55 per developer a month (free under 10); LinearB $29 to $59 per contributor a month, 50-seat minimum |
| DORA metrics and cycle-time phases | Apache DevLake | Free, on servers you run (Docker) |
| Org catalog, owners, scorecards, campaigns | Cortex, OpsLevel, Port | Port from $30 a seat a month (free up to 15); Cortex and OpsLevel by quote |
| Update-bot hygiene and package verdicts | Renovate's dashboard, Socket | Socket from $25 a seat a month |
| Open-source community health | LFX Insights, CHAOSS tools | LFX for Linux Foundation projects; CHAOSS tools self-hosted |
Public list prices as of October 2026. StackVitals covers the core workflows of these tools for GitHub-first teams.
Yes. It runs in your own GitHub Actions minutes (about a minute a run) and keeps everything in your repo. There is no StackVitals service to pay for or sign up to.
Yes. The workflow is the same. GitHub Pages sites are public, so a private repo's app opens on your machine with stackvitals ui owner/repo, or in the app here with a token that can read the repo.
Into a branch called stackvitals-data in your own repo, and nowhere else, unless you add a chat webhook yourself.
Only what someone with access asks for: a /stackvitals command or a request from the app is checked against that person's GitHub access before anything is recorded or changed.
It covers the core workflows of the tools in the table for GitHub-first teams. It doesn't do investment allocation, surveys, hosted runners or on-call.
Delete the workflow file, delete the stackvitals-data branch and turn GitHub Pages off. Nothing is left anywhere else.