Everything nixkeeper knows about one nixpkgs package: its nixpkgs version against upstream's (Repology, nixkeeper's own update checks), master's version, Hydra's latest builds on each platform with why a failure failed and when it last built, the update bot's (nixpkgs-update, r-ryantm) latest attempt and when it tries next, open update PRs and other PRs and issues, CVEs and advisories with nixkeeper's verdict against nixpkgs' version, maintainers and teams; an update merged into staging or staging-next on its way to master (stagingPR, and how it builds there), and whether staging-next breaks the package (stagingNextBreaks: a forecast). newerInDigests: what the hourly digests have that's newer than the dashboard's last sync.

Find nixpkgs packages by name (exact, then starting with, then containing the query), each with its status: failed, outdated, up to date, vulnerable.

Packages that need attention, as nixkeeper's dashboard counts them: a build failing on Hydra, outdated, vulnerable, or a CVE fix to backport; optionally only one maintainer's (GitHub handle), one team's or one list's, one kind, one platform. Without maintainer, team or list: all of nixpkgs (thousands: narrow with kind). With a maintainer or team, also the open PRs they can merge now with the merge bot (canMerge).

All of nixpkgs at a glance, from nixkeeper's dashboard: how many packages are outdated, failing to build, failing their update attempts, vulnerable, broken; the newest and longest-standing of each; the failing dependencies blocking the most builds; why builds and the update bot fail, grouped; what was fixed in the last week.

Search Hydra's builds of nixpkgs master (the builds digest, hourly) that aren't ok: failed (the package's own failure, with why from its log and an excerpt), dependency (blockedBy: which dependency failed), unfinished, queued. Newest first, or longest failing first. With the last success of each.

Search nixpkgs' open pull requests (the PR digest, hourly), with what the digest makes of each: its buckets (update, init, drop, tiny, bot, python, ...), the update it makes and how it compares with nixpkgs now (state), whether a maintainer can merge it with the merge bot, whether it blocks the update bot, duplicates, and packages it touches that fail on Hydra (maybe its fix).

Search nixpkgs' open issues by title (the PR digest, hourly). Build-failure issues have hydra: what Hydra builds now say (builds: a candidate to close; failing; waiting; removed; ...); update requests have update: whether nixpkgs has the version asked (done, partly, open) and the update bot's plans.

nixpkgs-update's (r-ryantm) latest attempt at packages (the update-bot digest, every 3 hours): its outcome, versions, PR, why it failed with a log excerpt; for one package, also its place in the bot's queue and when it's expected to try again.

CVEs from the NixOS security tracker (with its issue, severity, affected versions, status on master and the release branches) and OSV advisories for language packages (the vulnerabilities digest, hourly): one package's, one CVE's (or NIXPKGS-..., or an advisory id), or else the CVEs affecting some package now, worst first.

When each digest and the dashboard were last made and read (their meta.json files), and what this server has cached.