revenant.
npm
65
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.

bower

“A venerable guide through the early days of frontend package management. Its contributions helped build the foundation upon which the modern web stands.”

epitaph by gemma-aistudio/gemma-4-26b-a4b-it · model heuristic-v1 · signals, not verdicts · snapshot from 2026-10-29

Last words: “CI: add Node.js 18, 20 & 22 (#2630)”

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
2 years ago

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

release gap
4.6 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
309,389

Recent weekly downloads from the package registry.

dependents
167,938

Public repositories or packages that depend on this project.

years active
14 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
    +40 pts
  • Time since last release
    +15 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 2+ years

    Last commit 2024-10-13T10:45:04Z

Living successors

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

Visit the repository (bower/bower) →

Día de los Muertos · Altar of Remembrance

Ofrenda

Every candle represents a person who gave time to bower. 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. @satazor1,327 commits
  2. @sheerun556 commits
Middle tier · Core contributors
  1. @sindresorhus130 commits
  2. @wibblymat76 commits
  3. @svnlto58 commits
  4. @fat28 commits
Lower tier · Community builders
  1. @necolas27 commits
  2. @josh23 commits
  3. @desandro23 commits
  4. @paulirish20 commits
It gave the world
309,389 downloads/week
Depended on by
167,938 public repos
Years of service
14 years

Hold a seance

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

Lighting the candles for maintainer support links…

Share the tombstone

ghost risk badge for bower

Embed the live README badge or share the memorial card:

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