revenant.
npm
33
ghost score
Fading

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.

ms

“ms still has a pulse. Long may it commit.”

epitaph by fallback-rules · model heuristic-v1 · signals, not verdicts · snapshot from 2026-10-29

Last words: “chore: minimumReleaseAge: 2880 (#289)”

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
5.3 months ago

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

release gap
5.9 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
488,210,519

Recent weekly downloads from the package registry.

dependents
2,318,159

Public repositories or packages that depend on this project.

years active
15 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
    +8 pts
  • Time since last release
    +15 pts
  • Zero active authors in past year
    +10 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

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

Visit the repository (vercel/ms) →

Día de los Muertos · Altar of Remembrance

Ofrenda

Every candle represents a person who gave time to ms. 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. @leo48 commits
  2. @rauchg36 commits
Middle tier · Core contributors
  1. @dimitropoulos22 commits
  2. @tj18 commits
  3. @styfle10 commits
  4. @Swatinem4 commits
Lower tier · Community builders
  1. @mrmckeb3 commits
  2. @leerob3 commits
  3. @greenkeeperio-bot2 commits
  4. @yuler2 commits
It gave the world
488,210,519 downloads/week
Depended on by
2,318,159 public repos
Years of service
15 years

Hold a seance

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

Lighting the candles for maintainer support links…

Share the tombstone

ghost risk badge for ms

Embed the live README badge or share the memorial card:

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