@mintlify/openapi-parsernpm
- latest 0.0.9
- last known licence MIT
- stars 16,395
- assessment attempted today
- GitHub evidence observed today
- 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 →Came back
After 12 months without a release, @mintlify/openapi-parser published 0.0.9 on 2026-10-01.
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 19 checks
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=18. Source: the registry.
- Publishers on the registry — 7. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — v.45 2/2 done; v.48 3/3 done; v.49 1/1 done; v.50 2/2 done; v.51 4/4 done. Source: the repository's milestones.
Third-party facts checked 24 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-11 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@mintlify/openapi-parser)Watch it
Get told when @mintlify/openapi-parser 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.