Liveness
Sato Hub's recency label — Active, Recent, Quiet or Dormant — from a listing's latest commit or release, never a post. A maintenance signal, not a risk grade.
Every listing's most recent code activity — the newer of its last commit and its last release — is refreshed daily. Liveness buckets the age of that timestamp: Active within 30 days, Recent within 90, Quiet within a year, Dormant beyond it. A post on X is news, not maintenance, so it never makes a listing Active; the listing page shows the last news post on its own line. When no commit or release is tracked, no label is shown rather than a guessed one: unknown, not stale.
The label feeds the maintenance component of the Sato Score and is what the directory's liveness badge displays. It is deliberately about observed activity rather than a project's own status field, because self-description drifts and commits do not.
Liveness is not uptime and not quality. A finished library can be Quiet and fine; a busy repo can be Active and broken. It also cannot see private activity, so closed-source projects read quieter than they are.
Where Sato Hub measures it
- Directory (liveness badge on every card) →
- Site-wide changelog of observed activity →
- Reliability index (cohorts by liveness) →
Numbers live on those pages and refresh on their own schedule; this definition does not restate them.
Related terms
Reference
SourcesWhere the data comes fromShowHide
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Liveness (glossary)." Sato Hub, updated 2026-10-24, accessed 2026-10-24. https://satohub.ai/glossary/livenessData last refreshed 2026-10-24; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.