npm package memorial
ℹ︎ How to read this score
lodash
“lodash 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: “ci: update actions to latest versions (#6279)”
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.
- Time since last release+4 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.
- No conclusive risk evidence recorded — absence of evidence is not evidence of absence.
Living successors
- lodash/lodashactive fork
Active fork — pushed 27d ago
Día de los Muertos · Altar of Remembrance
Ofrenda
Every candle represents a person who gave time to lodash. 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 lodash 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 lodash 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/lodash)