npm package memorial
ℹ︎ How to read this score
request
“A foundational pillar of the Node.js ecosystem that carried the weight of the web for over a decade. Its legacy remains woven into the fabric of countless modern applications.”
epitaph by gemma-aistudio/gemma-4-26b-a4b-it · model heuristic-v1 · signals, not verdicts · snapshot from 2026-10-29
Last words: “README: typo in deprecation message (#3268)”
Vital signs
hover or focus any vital for threshold guidanceWeekly commit cadence over the last 6 months; flatlined means 0 recent commits.
Threshold: >365 days without a commit strongly elevates ghost risk.
Threshold: >365 days since the latest registry release.
Share of commits by the single top author; >=80% means reliance on one person.
Share of issues closed over the past year; <25% can signal backlog pressure.
Recent weekly downloads from the package registry.
Public repositories or packages that depend on this project.
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.
- Registry deprecation flag+65 pts
- Time since last commit+40 pts
- Time since last release+15 pts
- Zero active authors in past year+10 pts
- Declining download trend+4 pts
Cause of death
Officially Deprecated
The maintainers published a formal registry deprecation notice guiding users toward newer alternatives.
- #1 · RegistryOfficially deprecated
request has been deprecated, see https://github.com/request/request/issues/3142
Living successors
- undicicurated
Officially recommended successor to request
- node-fetchcurated
Fetch API surface for Node
- axioscurated
Widely maintained HTTP client
Día de los Muertos · Altar of Remembrance
Ofrenda
Every candle represents a person who gave time to request. 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.
Hold a seance
The spirit of request 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 request did, how to migrate away, or how it ended.
Share the tombstone
Embed the live README badge or share the memorial card:
[](http://localhost:3000/grave/npm/request)