@nymproject/mix-tunnelnpm
- latest 0.3.1
- last known licence Apache-2.0
- stars 1,984
- assessment attempted 16 days ago
- GitHub evidence observed 16 days ago
- registry checked 16 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
100
Open issues
154
Unanswered
24
Contributors
10
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 5. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — Temporary Home 21/26 done; Independent Release 122/124 done; Fuqing - (mainnet release 29th sept) (due 2026-09-16) 10/10 done; Glasgow - (mainnet release 13th oct) (due 2026-09-30) 4/22 done; Hanoi - (mainnet release 27th oct) (due 2026-10-14) 0/2 done. Source: the repository's milestones.
- OpenSSF Scorecard — 4.4 / 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 on 2026-09-26; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-26 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@nymproject/mix-tunnel)Watch it
Get told when @nymproject/mix-tunnel 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.