- Listed servers
- The number of live listings our crawl holds for the registry, after the registry's own duplicates are collapsed (two listings of the same repository count once). A listing is live under the same rule the leaderboard uses: registries we sync incrementally keep a listing until the registry marks it deleted; registries we re-crawl in full keep a listing for 30days after our last sighting of it. Where a registry's public API returns a bounded page of its catalog, the count is a floor — see that registry's caveats.
- 30-day change and trend
- The series is reconstructed day by day from when each listing was first and last seen, using the liveness rule above, so its newest point equals the current count. A flat segment can be the registry or our crawl — the caveats say which when we know.
- Last sync
- The newest sighting our crawl wrote for the registry, on our clock. For incrementally synced registries this is the newest changed listing the feed returned, which can trail the run time on quiet days.
- Newest published listing
- The newest publish or creation date the registry itself reported for a listing, among everything our crawls fetched in the last 45 days — the registry's clock, not ours, capped at the last sync. It shows how recent the newest listing the registry returned is, which is a different question from when we last fetched it.
- Status
- Fresh: a sighting within 3 days. No new data: none for longer than that — the page reports the date and nothing more. Unchanged: crawls keep landing but no listing has been seen for the first time in 14days, which is what a crawl returning an identical catalog looks like. Freshness windows count back from the registry's own newest sighting, never the wall clock, so a paused feed freezes its numbers rather than draining them.
Caveats are hand-maintained, dated notes about behaviour we observed while crawling; they describe our measurement, not the registry. The registry list, cadences and deduplication method are on /sources; how the ranking itself works is on /methodology. Registry operators who spot a measurement error can write to hello@biff.ai.