@lottiefiles/lottie-playernpm
This package has dated incident reports relevant to its trust history. Check the affected releases and the response before drawing conclusions about its current version.
Read the incident coverage →- latest 2.0.12
- last known licence MIT
- stars 1,657
- assessment attempted 25 days ago
- 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 10 checks
What the project says about itself
- Build provenance — the latest release, 2.0.12, carries a signed provenance attestation. Source: the registry.
- Publishers on the registry — 2. Source: the registry.
- OpenSSF Scorecard — 4.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 25 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-12 | first verdict: abandoned |
Supply-chain history 1
-
account hijacked 2024-10 2.0.5, 2.0.6, 2.0.7
A compromised publish token pushed three releases in an hour that injected a crypto-wallet connection prompt into sites embedding the player.
The versions were removed and 2.0.8 published with the same content as 2.0.4.
Source: Snyk analysis, 31 October 2024. History, not a warning about today — the verdict above is about maintenance now.
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@lottiefiles/lottie-player)Watch it
Get told when @lottiefiles/lottie-player 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.