@visx/react-spring
visx primitives that rely on react-spring for animation
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate migration from personal npm account to GitHub Actions CI/CD with SLSA provenance. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer list change consistent with airbnb/visx monorepo team management. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 5 / 1 | |
| 3.12.0 | 7 / 0 | |
| 3.10.1 | 7 / 0 | |
| 3.9.0 | 7 / 0 | |
| 3.8.0 | 7 / 0 | |
| 3.5.1 | 7 / 0 | |
| 3.5.0 | 7 / 0 | |
| 3.4.1 | 7 / 0 | |
| 3.4.0 | 7 / 0 | |
| 3.3.0 | 7 / 0 | |
| 3.2.0 | 7 / 0 | |
| 3.1.0 | 7 / 0 | |
| 3.0.1 | 7 / 0 | |
| 3.0.0 | 7 / 0 |
v3.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.