revenant.
npm
4
ghost score
Alive

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.

p-limit

“A vital heartbeat in the JavaScript ecosystem, managing concurrency with quiet precision. It remains a steadfast companion to millions of developers worldwide.”

epitaph by gemma-aistudio/gemma-4-26b-a4b-it · model heuristic-v1 · signals, not verdicts

Last words: “Meta tweaks”

Vital signs

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

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

last commit
43 days ago

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

release gap
43 days

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
259,168,839

Recent weekly downloads from the package registry.

dependents
1,094,175

Public repositories or packages that depend on this project.

years active
10 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
  • Zero active authors in past year
    +10 pts
  • Recent release published (mitigation)
    -6 pts

Cause of death

Active & Maintained

Recent commits, releases, or maintainer activity indicate a healthy, living project.

  1. No conclusive risk evidence recorded — absence of evidence is not evidence of absence.

Living successors

Visit the repository (sindresorhus/p-limit) →

Día de los Muertos · Altar of Remembrance

Ofrenda

Every candle represents a person who gave time to p-limit. 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. @sindresorhus63 commits
  2. @LinusU2 commits
Middle tier · Core contributors
  1. @jdmarshall2 commits
  2. @sugoroku-y1 commits
  3. @tuhm11 commits
  4. @sethp1 commits
Lower tier · Community builders
  1. @liuhanqu1 commits
  2. @zkochan1 commits
  3. @rajanpanth1 commits
  4. @schnittstabil1 commits
It gave the world
259,168,839 downloads/week
Depended on by
1,094,175 public repos
Years of service
10 years

Hold a seance

The spirit of p-limit 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 p-limit did, how to migrate away, or how it ended.

Lighting the candles for maintainer support links…

Share the tombstone

ghost risk badge for p-limit

Embed the live README badge or share the memorial card:

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