fxa-crypto-reliernpm
- latest 2.7.0
- last known licence MPL-2.0
- stars 3
- assessment attempted 23 days ago
- GitHub evidence observed 23 days ago
- registry checked 23 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
4
Unanswered
2
Contributors
0
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=6. Source: the registry.
- Publishers on the registry — 2. Source: the registry.
- Open milestones — FxA-0: quality; FxA-157: Email service improvements; FxA-158: db migration issues; FxA-156: Fenix Pairing flow (due 2018-12-31) 1/1 done; FxA-512: Feature-flagging (due 2019-03-29). Source: the repository's milestones.
- OpenSSF Scorecard — 3.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 23 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-24 | first verdict: abandoned |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/fxa-crypto-relier)
Watch it
Get told when fxa-crypto-relier 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.