revenant.
npm
100
ghost score
Departed
✝ archived⚠ deprecated

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.

protractor

“protractor stepped aside with a note pinned to the door. It told you where to go next — that is a kind of care.”

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

Last words: “build: publish using wombat”

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

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

release gap
6.5 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
436,642

Recent weekly downloads from the package registry.

dependents
615,722

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
  • Repository archived (read-only)
    +70 pts
  • Registry deprecation flag
    +65 pts
  • Time since last commit
    +40 pts
  • Time since last release
    +15 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. #1 · RegistryOfficially deprecated

    We have news to share - Protractor is deprecated and will reach end-of-life by Summer 2023. To learn more and find out about other options please refer to this post on the Angular blog. Thank you for using and contributing to Protractor. https://goo.gle/state-of-e2e-in-angular

Living successors

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

Visit the repository (angular/protractor) →

Día de los Muertos · Altar of Remembrance

Ofrenda

Every candle represents a person who gave time to protractor. 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. @juliemr717 commits
  2. @cnishina232 commits
Middle tier · Core contributors
  1. @sjelin150 commits
  2. @hankduan104 commits
  3. @heathkit66 commits
  4. @qiyigg28 commits
Lower tier · Community builders
  1. @andresdominguez21 commits
  2. @elgalu15 commits
  3. @el-davo15 commits
  4. @NickTomlin13 commits
It gave the world
436,642 downloads/week
Depended on by
615,722 public repos
Years of service
14 years

Hold a seance

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

Lighting the candles for maintainer support links…

Share the tombstone

ghost risk badge for protractor

Embed the live README badge or share the memorial card:

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