@types/dom-parsernpm
- latest 1.1.5
- last known licence MIT
- stars 51,444
- assessment attempted today
- registry checked 14 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 2 years without a release, @types/dom-parser published 1.1.5 on 2026-10-28.
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 11 checks
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 1. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — Breaking changes 5/7 done. Source: the repository's milestones.
- OpenSSF Scorecard — 6.5 / 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 6 days ago; registry facts on every crawl.
State history 2
| When | Change |
|---|---|
| 2026-11-05 | active → abandoned |
| 2026-10-12 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@types/dom-parser)Watch it
Get told when @types/dom-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.