animated
Declarative Animations Library for React and React Native
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): intelligibabble and vjeux are well-known React/React Native contributors at Facebook; this is a documented legitimate team transition for the animatedjs library. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): es6-set, invariant, and tinycolor are all well-established, benign packages appropriate for an animation library. No malicious packages introduced. | ai | |
| phantom-deps | phantom-dep:tinycolor | AI (phantom-deps): tinycolor is referenced in config files for color animation support; phantom-dep finding is a false positive for this package's use case. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from intelligibabble to browniefed occurred in 2018; browniefed has since published multiple approved versions of this package, confirming a legitimate settled transition. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.2.2 | 2 / 12 | |
| 0.2.1 | 2 / 11 | |
| 0.2.0 | 2 / 11 | |
| 0.1.5 | 2 / 11 | |
| 0.1.4 | 3 / 11 | |
| 0.1.3 | 3 / 11 | |
| 0.1.2 | 3 / 11 | |
| 0.1.1 | 3 / 11 | |
| 0.1.0 | 0 / 0 |
v0.2.2
2 findingsThis version was published by a different npm account than previous versions on 2018-02-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-11-09. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-02-07. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-12-31. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-11-14. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-04-10. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.