Dependency health Main page Pro coming soon

Dependency maintenance, made clearer

Fewer surprises.
Clearer decisions.
Keep building.

Spot fading maintenance, licence changes and deprecation in the open-source packages you rely on.

Check a project →Explore packages →
Start with a public manifest. No account needed.
Packages assessed518,930Unique packages; repeat crawls do not increase this countView packages →Actively maintained108,171Regular development activityView packages →Worth a closer look59,288Drifting, abandoned or deadView packages →Ecosystems covered11One place to check your stackView packages →

Choose with context.

See the maintenance evidence before you add a dependency.

Find a package →

Know what needs attention.

Turn a manifest into an explained maintenance review list.

Check your project →

Keep your team informed.

Watch selected packages and get alerts when things change.

Build your watchlist →

Fits the way you work

From the first dependency
to the next release.

Add maintenance context alongside your existing delivery and security tools.

See where isitdeadyet fits →CI, inventory and setup guide →

From the catalog

Live feed

All recent changes →

  1. request

    abandoned · npm

    Was dead. request is abandoned by its maintainers' own account — the README says it is no longer maintained, no commits for over 6 years. Plan a migration rather than waiting for a fix.

    ·

  2. audit-ci

    abandoned · npm

    Was finished. audit-ci appears abandoned — last commit 22 days ago. 4 of 19 open issues have had no reply. Plan a migration rather than waiting for a fix.

    ·

  3. @types/enzyme-to-json

    abandoned · npm

    Was active. @types/enzyme-to-json appears abandoned. No issue data available. Plan a migration rather than waiting for a fix.

    ·

Beyond maintenance

Supply-chain news

All reports →

Latest security headlines · automated leads, not confirmed package findings. Last news check: .

Make maintenance a planned decision

Your next step starts
with what you depend on.

Check a project →Find your plan →
How we assess maintenance

The six verdicts

  • active Work is landing and issues get answers.
  • coasting A settled project. Nothing needs doing right now.
  • finished Complete. A new commit would be noise, and nobody is waiting on one.
  • drifting Something is slipping. Worth watching before it becomes a problem.
  • abandoned Nobody is home and users are waiting. Plan a migration.
  • dead Gone. Anything depending on it should be replaced.
VerdictTrigger
active A commit in the last 90 days.
coasting No commits for 90–365 days, with nothing else deteriorating.
finished No commits for over 365 days, and almost nobody filing new issues — or the README says the project is done.
drifting No commits for 180–365 days plus a deterioration signal: unanswered issues rising, maintainers down to one, or issue response time doubling.
abandoned No commits for over 365 days with unanswered issues piling up — or the registry marks it deprecated, or the repository is archived.
dead The repository is archived and the registry marks it deprecated, or the package has been removed from the registry.

An issue counts as unanswered once it has gone 14 days without a reply. Nothing changes verdict on a single bad day either: a new state has to hold across two crawls at least 7 days apart before we act on it. The exceptions are facts rather than inferences — an archived repository or a registry deprecation counts immediately.