@ampproject/amp-date-countdownnpm
- latest 1.2110011758.0
- last known licence Apache-2.0
- stars 14,906
- assessment attempted today
- GitHub evidence observed yesterday
- registry checked 11 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 10 checks
Commits 90d
11
Open issues
941
Unanswered
19
Contributors
19
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 16. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — Backlog Bugs 1697/1709 done; 3P Implementation 154/154 done; Docs Updates 405/407 done; Pending Triage 1378/1384 done; Active Non-Sprint Tracked 159/159 done. Source: the repository's milestones.
- OpenSSF Scorecard — 9.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 6 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-06 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@ampproject/amp-date-countdown)Watch it
Get told when @ampproject/amp-date-countdown 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.