Dispute an observation

How to contest an observation

Send the component identifier (owner/repo or a package coordinate) and the state you assert, to [email protected].

Evidence required: a public URL showing the entity resolves — HTTP 200, not archived — together with its last-commit date. That is the read we re-run.

Response: within 5 business days.

Corrections: a correction is dated and shown on the component's page. The prior observation is kept; the series is append-only.

Methodology

Every reported state is a point-in-time read against the GitHub public REST API. The exact day thresholds:

Observed vs ingested

Each row records whether it is our own dated read (observed) or was seeded from a public census and re-read (ingested), with its own source. The daily continuity series is our own observation; the census population was ingested and re-read against the API.

Unknown-stale rule

A verdict of alive, dormant, or abandoned rests on an activity observation. When the observation it rests on is itself older than the 180-day threshold, the verdict is withheld as unknown-stale: the observation was not re-verified, so a present-tense state is not derived from it. Unknown-stale is not a death; it is the absence of a derivable verdict.

Known gaps

There was no full re-probe on 2026-07-30. Any state transition on that date is interval-censored — bounded between the surrounding observations, not dated to that day. A component not observed returns not-checked, never gone; a gap between observations is never interpolated.