@asamuzakjp/generational-cachenpm

Verdict

Looks abandoned

@asamuzakjp/generational-cache appears abandoned — its repository has been archived, no commits for 2 months. There are no open issues. Plan a migration rather than waiting for a fix.

health 10/100

Why this verdict?

abandoned — No commits for over 365 days with unanswered issues piling up — or the registry marks it deprecated, or the repository is archived.

repository archived

Judged on 2026-09-13 from signal heuristics. How each verdict is decided

latest 3.0.1
licence MIT
stars 0
assessment attempted on 2026-09-13
registry checked 2 days ago
registry ↗
repository ↗

Vulnerabilities, end of life and next steps

Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.

Review remediation options →

Maintenance trends

Loading historical repository activity…

Signals · last 2 checks

Commits 90d

Open issues

Unanswered

Contributors

What the project says about itself

Build provenance — the latest release carries no provenance attestation. Source: the registry.
Supported runtime — node ^22.13.0 || >=24.0.0. Source: the registry.
Publishers on the registry — 1. Source: the registry.
Security policy — published. Source: the repository.

Third-party facts checked on 2026-09-12; registry facts on every crawl.

State history 1

When	Change
2026-09-13	first verdict: abandoned

Badge

Drop this in your README. It re-renders itself as the verdict changes.

[![maintenance](https://isitdeadyet.dev/badge/npm/@asamuzakjp/generational-cache.svg)](https://isitdeadyet.dev/npm/@asamuzakjp/generational-cache)

Watch it

Get told when @asamuzakjp/generational-cache changes state, changes licence, or is deprecated — instead of finding out during an incident.

Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.