@node-lightning/cryptonpm
- latest 0.28.0
- last known licence MIT
- stars 138
- assessment attempted 20 days ago
- GitHub evidence observed 20 days ago
- registry checked 17 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
0
Open issues
38
Unanswered
36
Contributors
0
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=10.17. Source: the registry.
- Publishers on the registry — 1. Source: the registry.
- Open milestones — Gossip Layer Complete 6/9 done; Channel Open/Close Complete 11/11 done. Source: the repository's milestones.
- OpenSSF Scorecard — 3.3 / 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 20 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-17 | first verdict: abandoned |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@node-lightning/crypto)Watch it
Get told when @node-lightning/crypto 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.