@angular/elementsnpm
- latest 22.2.4
- last known licence MIT
- stars 101,126
- assessment attempted yesterday
- GitHub evidence observed yesterday
- registry checked 20 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 27 checks
Commits 90d
100
Open issues
846
Unanswered
113
Contributors
21
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node ^22.22.3 || ^24.15.0 || >=26.0.0. Source: the registry.
- Publishers on the registry — 2. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — Backlog 25665/26342 done; needsTriage 10582/11046 done; docs-infra-a11y 18/18 done; docs-infra-tooling 372/372 done; docs-infra-aio-app 213/213 done. Source: the repository's milestones.
- OpenSSF Scorecard — 8.3 / 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 30 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-05 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@angular/elements)Watch it
Get told when @angular/elements 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.