revenant.
npm
50
ghost score
Haunted

npm package memorial

ℹ︎ How to read this score
Signals, not verdicts. A ghost score (0–100) estimates the probability that a repository will go 12 months without a non-bot commit, become archived, or be deprecated. A high score is a prompt to check your dependency health — never an accusation against its maintainers.

detect-libc

“detect-libc did not die — it faded, release by release, until the pulse went flat.”

epitaph by fallback-rules · model heuristic-v1 · signals, not verdicts

Last words: “Release v2.1.2”

Vital signs

hover or focus any vital for threshold guidance
commit pulse (26 wks)
flatlined

Weekly commit cadence over the last 6 months; flatlined means 0 recent commits.

last commit
1.1 years ago

Threshold: >365 days without a commit strongly elevates ghost risk.

release gap
1.1 years

Threshold: >365 days since the latest registry release.

bus factor
not enough data

Share of commits by the single top author; >=80% means reliance on one person.

issue close rate
not enough data

Share of issues closed over the past year; <25% can signal backlog pressure.

weekly downloads
193,006,254

Recent weekly downloads from the package registry.

dependents
2,309,281

Public repositories or packages that depend on this project.

years active
9 years

Time elapsed since the package's first recorded release.

What pushed this score up or down

Transparent signal attribution — positive points increase ghost risk, green negative points reflect active mitigations.

model: heuristic-v1
  • Time since last commit
    +30 pts
  • Time since last release
    +10 pts
  • Zero active authors in past year
    +10 pts

Cause of death

Gradual Dormancy

No sudden announcement — commits and releases gradually spaced out until activity went quiet.

  1. #1 · CommitNo commits in 13 months

    Last commit 2025-10-05T12:44:12Z

Living successors

No replacement needed or no drop-in successor registered. Check the repository before planning a migration.

Visit the repository (lovell/detect-libc) →

Día de los Muertos · Altar of Remembrance

Ofrenda

Every candle represents a person who gave time to detect-libc. In the Día de los Muertos tradition, an ofrenda welcomes back the memory of those who came before — honoring the hands that built the software we rely on.

Upper tier · Lead stewards
  1. @lovell59 commits
  2. @coreprocess4 commits
Middle tier · Core contributors
  1. @styfle2 commits
  2. @dstaley1 commits
  3. @malept1 commits
  4. @Mike-Dax1 commits
Lower tier · Community builders
  1. @H4ad1 commits
  2. @fastman1 commits
  3. @lambdalisue1 commits
It gave the world
193,006,254 downloads/week
Depended on by
2,309,281 public repos
Years of service
9 years

Hold a seance

The spirit of detect-libc answers strictly from its own records — README, releases, and issues. It never impersonates a maintainer and says “I don't remember that” when evidence is missing.

The candles are lit. Pick a question above or ask what detect-libc did, how to migrate away, or how it ended.

Lighting the candles for maintainer support links…

Share the tombstone

ghost risk badge for detect-libc

Embed the live README badge or share the memorial card:

[![ghost risk](http://localhost:3000/api/badge/npm/detect-libc.svg)](http://localhost:3000/grave/npm/detect-libc)
Share on XOpen OG card (PNG)