Show HN: StackVitals – CI failure triage and DORA metrics, no server

StackVitals launched as a free, open-source developer suite that runs entirely inside a repository's own GitHub Actions to triage CI failures and track DORA delivery metrics, with no StackVitals-hosted backend, account or subscription. When CI fails on a pull request, StackVitals posts one comment sorting each failure from the repo's own CI history — for example flagging a test that "flaked 6 times in 80 runs in the last 30 days" as likely flaky — while the verdict check still blocks until CI is green, re-running known flakes rather than waving them through. The tool installs as the GitHub Action stackvitals/stackvitals@v0 or via `pip install stackvitals`, publishes a dashboard to GitHub Pages for public repos, and keeps private-repo data local through `stackvitals ui owner/repo`.

The vital signs of your GitHub repo. Flaky tests, slow reviews, delivery and DORA, risky dependencies and community health, measured in your own GitHub Actions. <sub A tour on demo data. Watch it with sound https://raw.githubusercontent.com/stackvitals/stackvitals/main/docs/assets/stackvitals-video.mp4 .</sub A free, open-source developer suite for GitHub: CI health and flaky tests, pull request flow, delivery and DORA, dependencies, community health and an org portal. It runs in your own GitHub Actions and keeps its history in your own repo: no StackVitals-hosted backend, account or subscription, and optional integrations use services and keys you choose. GitHub's built-in token covers every module in a repo; an org's private repos in the Portal need a read-only App, and org-wide Copilot usage an org token. Actions minutes on private repos are billed by GitHub as usual docs/scaling.md https://github.com/stackvitals/stackvitals/blob/main/docs/scaling.md actions-minutes-private-repos . The rules behind its verdicts are checked on public data, with the losses published. Every run publishes an app on your repo's GitHub Pages or stackvitals ui owner/repo on your machine : one page per module, decisions and settings saved straight from the browser, setup for more repos in a few clicks once GitHub is connected connecting takes one token, made from a prefilled GitHub page; Pages are turned on for public repos , and a demo at ?demo=1 . docs/app.md https://github.com/stackvitals/stackvitals/blob/main/docs/app.md walks through it. Install it as the GitHub Action stackvitals/stackvitals@v0 also on the GitHub Marketplace https://github.com/marketplace/actions/stackvitals , or the CLI and MCP server from PyPI: pip install stackvitals or run it without installing: uvx stackvitals . When CI fails on a pull request, one comment sorts each failure, from the repo's own CI history: StackVitals: about this CI failure 1 of 3 failure s look like flakes; the rest need a look. Verdict What failed Why Likely flaky test t::flaky one flaked 6 times in 80 runs in the last 30 days, last 2026-10-20, and the message shows a flake's sign "TimeoutError" : looks like a flake, check the error, then re-run it New test t::new one no earlier flakes: likely from this change fails with "assert result == 2" Already failing on main test t::broken one also failing on the default branch, not caused by this change The verdict check still blocks until CI is green: a known flake is re-run, never waved through. pip install stackvitals gh auth login once, so StackVitals can use your GitHub sign-in stackvitals init your-name/your-repo init adds one workflow file to your repo, runs it once and turns on your dashboard: - Public repo: the dashboard goes live at https://your-name.github.io/your-repo/ . - Private repo: your data stays in your private repo, and the dashboard opens on your machine: stackvitals ui your-name/your-repo Just looking? stackvitals ci report owner/repo reports CI health for any public repo in about 20 seconds, with nothing added to it. Prefer clicking? The app's Setup page does the same as init . More: docs/quickstart.md https://github.com/stackvitals/stackvitals/blob/main/docs/quickstart.md . Every step, from what starts a run to what you see: the architecture in detail https://github.com/stackvitals/stackvitals/blob/main/docs/architecture.md . | Module | What it answers | Status | |---|---|---| | CI Health https://github.com/stackvitals/stackvitals/blob/main/docs/modules.md ci-health | Which jobs and tests are flaky or slowing down, who owns them, coverage and patch coverage | stable | | Team Flow https://github.com/stackvitals/stackvitals/blob/main/docs/modules.md team-flow | Who has to act next on each pull request, and how long reviews take | stable | | Delivery https://github.com/stackvitals/stackvitals/blob/main/docs/modules.md delivery-cycle-time-and-dora | Cycle time split into coding, pickup, review and deploy LinearB's phases , DORA's five metrics, AI-assisted work compared like with like | stable | | Insights https://github.com/stackvitals/stackvitals/blob/main/docs/modules.md insights-what-to-fix-first | What to fix first across modules, ranked by hours lost, with alerts and a weekly digest | stable | | Dependency Steward https://github.com/stackvitals/stackvitals/blob/main/docs/modules.md dependency-steward | Known vulnerabilities and malware in the lockfiles OSV-Scanner reads npm, PyPI, Go, Rust, Maven, Ruby, .NET, PHP and more; 65 of 100 sampled repos had one ; whether to add, keep or upgrade a package, with upgrade evidence from public repos | preview | | Community https://github.com/stackvitals/stackvitals/blob/main/docs/modules.md community | Where newcomers drop out, how fast they get an answer, who carries the work | stable | | Portal https://github.com/stackvitals/stackvitals/blob/main/docs/modules.md portal | A lightweight catalog on GitHub alone: what an org owns, who owns it checked , scorecards, golden paths and an org-wide view | preview | | Explore | SQL over your repo's data in the browser, with links to share a query | preview | | Contribute https://github.com/stackvitals/stackvitals/blob/main/docs/modules.md contribute-mergescout | Open-source issues an outsider can realistically get merged | stable | Stable: measured, reviewed and used on the sandbox for every release. Preview: built and tested, but newer or measured on less; its behaviour may still change. Works with Jira Cloud, Linear, PagerDuty, incident.io, Copilot usage reports, Slack, Teams, Discord, Discourse, test reports from other CI systems, Backstage, and DevLake's tables docs/connectors.md https://github.com/stackvitals/stackvitals/blob/main/docs/connectors.md . AI agents get every module through one MCP server 11 core tools by default, all 35 with --tools all . Everything works with GitHub's built-in token. Integrations are optional; pass their keys as repository secrets: - uses: stackvitals/stackvitals@v0 with: webhook: ${{ secrets.SLACK WEBHOOK }} alerts to Slack, Teams or Discord pagerduty-token: ${{ secrets.PAGERDUTY TOKEN }} incidents count in DORA jira-email: ${{ secrets.JIRA EMAIL }} Jira, with its site URL under jira-token: ${{ secrets.JIRA TOKEN }} connectors.jira in .github/stackvitals.toml Every input: docs/install.md https://github.com/stackvitals/stackvitals/blob/main/docs/install.md . Every setting: docs/settings.md https://github.com/stackvitals/stackvitals/blob/main/docs/settings.md . Your coding agent can ask StackVitals before and while it changes code: is this failure a known flake? , what is blocking PR 123? , who should review this? , is this package safe to add? It answers from your repo's history, with the evidence. Claude Code: claude mcp add stackvitals -- uvx stackvitals serve Claude Desktop, Cursor, VS Code and other MCP clients: { "mcpServers": { "stackvitals": { "command": "uvx", "args": "stackvitals", "serve" } } } It uses your gh login or GITHUB TOKEN . The 11 core tools load by default ci failure , is known flake , pr queue , who should review , check package , insights and more ; stackvitals serve --tools all loads all 35. Listed in the MCP registry as io.github.stackvitals/stackvitals . Measured on public repos beside the rules other tools use docs/accuracy.md https://github.com/stackvitals/stackvitals/blob/main/docs/accuracy.md : - Where you deploy from. With no setup, StackVitals named the right deployment source for 53 of 60 repos 30 of 35 held out . On the same 60, DevLake's default pattern got 9 and a pattern a user would typically write got 22. A wrong source makes every DORA number wrong. - Who answered an issue. Of the first comments by non-maintainers that the github/issue-metrics action counts as the answer, 46% are drive-bys 40-52%, held-out repos . StackVitals counts the project's answers: maintainers, regular responders and triagers. - Whether AI help changed anything. Agents' pull requests look 9 points less likely than people's to be merged by someone else. Compared within the same repo, month and size, the gap is +0.5 points 0.0 to +1.1 : most of the raw gap comes from which repos agents work in and the size of their changes. It publishes what failed too. Of the failures an old rule called safe to re-run, 44% 15 of 34 were caused by the change. The tightened rule still got 13 of 81 held-out calls wrong 16% . A stricter one a flake's sign in the log, no changed file named got none of 4 fresh calls wrong, too few to show 5%, so nothing is called safe: likely flakes are re-run, never passed by the check. Each sample was labelled by two model families Claude and Gemini ; no person has audited the labels. What each one does better, what StackVitals does differently, and what was measured side by side docs/compare https://github.com/stackvitals/stackvitals/blob/main/docs/compare/README.md : | Compared with | Kind | |---|---| | Apache DevLake https://github.com/stackvitals/stackvitals/blob/main/docs/compare/devlake.md | Open source Apache 2.0 , self-hosted | | Middleware https://github.com/stackvitals/stackvitals/blob/main/docs/compare/middleware.md | Open source Apache 2.0 , self-hosted | | CDviz https://github.com/stackvitals/stackvitals/blob/main/docs/compare/cdviz.md | Open source Apache 2.0 , self-hosted or EUR 20/month hosted | | Pelorus https://github.com/stackvitals/stackvitals/blob/main/docs/compare/pelorus.md | Open source Apache 2.0 , on OpenShift | | Liatrio's DORA plugin for Backstage https://github.com/stackvitals/stackvitals/blob/main/docs/compare/liatrio-backstage.md | Open source Apache 2.0 | | Faros Community Edition https://github.com/stackvitals/stackvitals/blob/main/docs/compare/faros-community-edition.md | Open source Apache 2.0 , withdrawn | | GrimoireLab https://github.com/stackvitals/stackvitals/blob/main/docs/compare/grimoirelab.md | Open source GPL-3.0 , self-hosted | | LinearB https://github.com/stackvitals/stackvitals/blob/main/docs/compare/linearb.md | SaaS; gitStream automation is free up to 250 PRs a month | | Swarmia https://github.com/stackvitals/stackvitals/blob/main/docs/compare/swarmia.md | SaaS; free up to 9 developers | | Trunk Flaky Tests and BuildPulse https://github.com/stackvitals/stackvitals/blob/main/docs/compare/flaky-test-tools.md | SaaS | - Five minutes: docs/quickstart.md https://github.com/stackvitals/stackvitals/blob/main/docs/quickstart.md . Try CI Health on any public repo first needs uv https://docs.astral.sh/uv/ and gh auth login or a GITHUB TOKEN : uvx stackvitals ci report owner/repo --days 14 --html ./ci-report . - By role: engineering managers https://github.com/stackvitals/stackvitals/blob/main/docs/guides/manager.md , maintainers https://github.com/stackvitals/stackvitals/blob/main/docs/guides/maintainer.md , platform teams https://github.com/stackvitals/stackvitals/blob/main/docs/guides/platform.md . - Before you rely on it: what each rule does https://github.com/stackvitals/stackvitals/blob/main/docs/rules.md , known limitations https://github.com/stackvitals/stackvitals/blob/main/docs/limitations.md , what leaves your repo https://github.com/stackvitals/stackvitals/blob/main/docs/privacy.md , threat model https://github.com/stackvitals/stackvitals/blob/main/docs/threat-model.md , enterprise controls https://github.com/stackvitals/stackvitals/blob/main/docs/enterprise.md . - More: FAQ https://github.com/stackvitals/stackvitals/blob/main/docs/faq.md , how it works https://github.com/stackvitals/stackvitals/blob/main/docs/architecture.md , roadmap https://github.com/stackvitals/stackvitals/blob/main/docs/roadmap.md , contributing https://github.com/stackvitals/stackvitals/blob/main/CONTRIBUTING.md , code of conduct https://github.com/stackvitals/stackvitals/blob/main/CODE OF CONDUCT.md , governance https://github.com/stackvitals/stackvitals/blob/main/GOVERNANCE.md , security https://github.com/stackvitals/stackvitals/blob/main/SECURITY.md .