@signalwire/compatibility-apinpm
- latest 3.2.1
- last known licence MIT
- stars 0
- assessment attempted 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 →Came back
After 13 months without a release, @signalwire/compatibility-api published 3.2.1 on 2026-10-16.
Usually this is a maintainer returning. It is also what a hijacked package looks like, so it is worth a glance at what changed before you upgrade.
Maintenance trends
Loading historical repository activity…
Signals · last 2 checks
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=16. Source: the registry.
- Publishers on the registry — 8. Source: the registry.
Third-party facts checked 20 days ago; registry facts on every crawl.
State history 2
| When | Change |
|---|---|
| 2026-10-17 | coasting → abandoned |
| 2026-09-16 | first verdict: coasting |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@signalwire/compatibility-api)Watch it
Get told when @signalwire/compatibility-api 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.