Canonical Stats
Measure the registry without inventing missing history.
These statistics are computed from the canonical machine index only. Unknown dates stay unknown, phased shutdowns remain phased, and no provider score or ranking is calculated.
Migration windows
Recorded migration-window coverage
Length is calculated only when a canonical start (`deprecated_at` or `announced_at`) and boundary (`migration_deadline_at`, `removal_effective_at`, or `sunset_at`) are both recorded.
| Bucket | Records | Share |
|---|
Lifecycle
Status and replacement coverage
Canonical status
Replacement type
Event types
Providers
Provider patterns in the reviewed dataset
Counts describe registry coverage only. They are not provider quality scores.
| Provider | Records | Removed / replaced | Still usable yes / partial |
|---|
Data quality
Evidence, freshness, and date coverage
Confidence
Freshness
Structured date coverage
Scope boundary
What these Stats do not claim
There is no structured deprecation-reason field in the current canonical schema, so this page does not manufacture a “reason” distribution from prose. Provider counts are coverage counts, not rankings. Missing migration dates are reported as unknown rather than estimated.