@endo/netstringnpm
- latest 1.1.1
- last known licence Apache-2.0
- stars 1,069
- assessment attempted 11 days ago
- GitHub evidence observed 11 days ago
- registry checked 12 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
62
Open issues
321
Unanswered
136
Contributors
6
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 9. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — distributed endo; local Endo (aka Exo) (due 2021-11-27) 11/11 done; XS Memory Safety Audit (due 2021-12-07); JS Compartments to Stage 2 (due 2021-12-07) 0/2 done; Endo 1 (due 2021-12-31) 5/6 done. Source: the repository's milestones.
- OpenSSF Scorecard — 8.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 11 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-28 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@endo/netstring)Watch it
Get told when @endo/netstring 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.