nanostorenpm
- latest 1.2.1
- licence MIT
- stars 9
- assessment attempted today
- GitHub evidence observed today
- 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 1 check
The first observation is recorded. Trend lines appear once at least two checks have data for the same signal.
Commits 90d
0
Open issues
0
Unanswered
0
Contributors
0
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 1. Source: the registry.
- Open milestones — 🌚 Week 35 (due 2020-08-28); 🛬 Week 36 (due 2020-09-04); 🐺 Week 37 (due 2020-09-11); ❓ Week 38 (due 2020-09-18); 🦗 Week 39 (due 2020-09-25). Source: the repository's milestones.
- OpenSSF Scorecard — 1.8 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.
Third-party facts checked today; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-19 | first verdict: abandoned |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/nanostore)Watch it
Get told when nanostore 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.