Dependency health Workspace Solo coming soon

@xen-orchestra/rest-apinpm

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 →
What the project says about itself
  • Build provenance — the latest release carries no provenance attestation. Source: the registry.
  • Supported runtime — node >=20.18. Source: the registry.
  • Publishers on the registry — 13. Source: the registry.
  • Open milestones — v6 70/181 done; backup 35/51 done; Pyrgos v1 (due 2024-06-28) 1/4 done; 2025 - Q1 (due 2025-03-31) 4/9 done; Somewhere in 2025 (due 2025-12-31) 7/29 done. Source: the repository's milestones.
  • OpenSSF Scorecard — 5.1 / 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 24 days ago; registry facts on every crawl.

State history 1
WhenChange
2026-10-22 first verdict: active

Badge

maintenance: active

Drop this in your README. It re-renders itself as the verdict changes.

[![maintenance](https://isitdeadyet.dev/badge/npm/@xen-orchestra/rest-api.svg)](https://isitdeadyet.dev/npm/@xen-orchestra/rest-api)

Watch it

Get told when @xen-orchestra/rest-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.