@xchainjs/xchain-cryptonpm
- latest 1.0.8
- licence MIT
- stars 134
- checked 4 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 1 check
The first observation is recorded. Trend lines appear once at least two checks have data for the same signal.
Commits 90d
68
Open issues
15
Unanswered
11
Contributors
6
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 11. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — DOGE support (due 2021-11-15) 1/1 done; Maintenance (due 2021-11-30) 20/20 done; Prepare @next version (due 2021-12-31) 1/1 done. Source: the repository's milestones.
- OpenSSF Scorecard — 6.2 / 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 4 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-09-14 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@xchainjs/xchain-crypto)Watch it
Get told when @xchainjs/xchain-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.