Health dashboard for nixpkgs packages: new releases, build and update failures, and vulnerabilities, in one place.
nixkeeper.com (every nixpkgs package) · demo (one maintainer's lists) · status · how it works
| Repository | What it is |
|---|---|
| nixkeeper | The dashboard: joins the digests into one page, every 3 hours. Fork it for a dashboard of your own lists |
| nixkeeper-mcp | MCP server, so an AI assistant can answer questions about nixpkgs packages from nixkeeper's data |
| status | Whether every sync, digest, test and token is on time, with an issue when one needs attention |
The digests: each reads one public source for all of nixpkgs and publishes what it finds, for nixkeeper and anyone else.
| Digest | Reads | Every |
|---|---|---|
| digest-builds | Hydra's latest evaluation of nixpkgs master (and staging-next, haskell-updates) | hour |
| digest-versions | Repology, GitHub releases and per-ecosystem indexes (CRAN, Emacs, Stackage, Typst) | 12 hours |
| digest-update-bot | nixpkgs-update's latest attempt at every package, and its queue | 3 hours |
| digest-vulnerabilities | The NixOS security tracker and OSV | hour |
| digest-prs | nixpkgs' open PRs and issues, sorted by what they change | hour |
- Find your packages on nixkeeper.com, by name or maintainer.
- A dashboard of your own: a fork with your package lists, about 15 minutes in GitHub's web pages.
- Get notified when your packages need attention.
- Ask an assistant with nixkeeper-mcp.
nixkeeper's code and documentation are written with the assistance of an AI (Claude, by Anthropic), with a person in the loop: its maintainer decides what to build, and reviews and tests every change before it's merged. The digests and syncs are automation that read public data. None of it ever comments on, closes or merges anything in nixpkgs.
nixkeeper is an independent community project, not affiliated with or endorsed by the NixOS Foundation. Everything here is MIT licensed.
