@aarsteinmedia/lottie-web
Play animations generated in After Effects in the browser
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/chunks/CanvasRenderer-IVulocR2.js | AI (source-diff): Rollup chunk output with long import lines; readable source, not obfuscated. Stable pattern for this build toolchain. | ai | |
| source-diff | net-exec-file:dist/chunks/InterfacesProvider-CgzYwLP_.js | AI (source-diff): Sampled code is plain TypeScript-compiled animation logic; no actual network calls or dynamic code execution visible. | ai | |
| source-diff | obfuscated-file:dist/lottie-canvas.js | AI (source-diff): Rollup-bundled animation library output; long lines are minification artifacts, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/lottie-canvas.js | AI (source-diff): Lottie renderer legitimately fetches animation JSON and renders dynamically; not dropper behavior. | ai | |
| source-diff | net-exec-file:dist/lottie-svg.js | AI (source-diff): Same pattern as lottie-canvas.js; expected for an SVG animation renderer. | ai | |
| source-diff | obfuscated-file:dist/chunks/CanvasRenderer-Ctb0G9eN.js | AI (source-diff): Rollup-bundled chunk with long lines; code is readable and benign — standard build output for this lottie fork. | ai | |
| source-diff | net-exec-file:dist/chunks/InterfacesProvider-BB-ZGMsj.js | AI (source-diff): Sample shows animation math/matrix code with no actual network calls or dynamic eval; false positive from heuristic on bundled chunk. | ai | |
| source-diff | net-exec-file:dist/chunks/InterfacesProvider-BNiH8_bt.js | AI (source-diff): Sample shows animation math/transform code; no actual network calls or dynamic code execution visible — Rollup chunk false positive. | ai | |
| source-diff | obfuscated-file:dist/chunks/CanvasRenderer-BBwd6iO9.js | AI (source-diff): Long lines are Rollup-generated minified bundle output, not obfuscation; readable class structure visible in sample. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 1.4.2 | 0 / 23 | |
| 1.4.1 | 1 / 22 | |
| 1.4.0 | 0 / 23 | |
| 1.3.13 | 0 / 23 | |
| 1.3.12 | 0 / 23 | |
| 1.3.11 | 0 / 23 | |
| 1.3.10 | 0 / 23 | |
| 1.3.9 | 0 / 23 | |
| 1.3.8 | 0 / 24 | |
| 1.3.7 | 0 / 23 | |
| 1.3.6 | 0 / 23 | |
| 1.3.5 | 0 / 24 | |
| 1.3.4 | 0 / 25 | |
| 1.3.3 | 0 / 26 | |
| 1.3.2 | 0 / 26 | |
| 1.3.1 | 0 / 26 | |
| 1.3.0 | 0 / 26 | |
| 1.2.1 | 0 / 26 | |
| 1.2.0 | 0 / 26 | |
| 1.1.10 | 0 / 26 | |
| 1.1.9 | 0 / 26 | |
| 1.1.8 | 0 / 26 | |
| 1.1.7 | 0 / 26 | |
| 1.1.6 | 0 / 26 | |
| 1.1.5 | 1 / 26 | |
| 1.1.3 | 1 / 26 | |
| 1.1.2 | 1 / 26 | |
| 1.1.1 | 0 / 26 | |
| 1.1.0 | 0 / 26 | |
| 1.0.15 | 0 / 26 | |
| 1.0.14 | 0 / 26 | |
| 1.0.13 | 0 / 26 | |
| 1.0.12 | 0 / 26 | |
| 1.0.11 | 0 / 26 | |
| 1.0.10 | 0 / 26 | |
| 1.0.9 | 0 / 26 | |
| 1.0.8 | 0 / 26 | |
| 1.0.7 | 0 / 26 | |
| 1.0.6 | 0 / 26 | |
| 1.0.4 | 0 / 26 | |
| 1.0.3 | 0 / 26 | |
| 1.0.2 | 0 / 25 | |
| 1.0.1 | 0 / 26 | |
| 1.0.0 | 0 / 26 |
v1.4.2
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.13
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.