@rive-app/react-webgl2
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 100 of 107)
| Version | Deps | Published |
|---|---|---|
| 4.30.0 | 1 / 0 | |
| 4.29.5 | 1 / 0 | |
| 4.29.4 | 1 / 0 | |
| 4.29.3 | 1 / 0 | |
| 4.29.2 | 1 / 0 | |
| 4.29.1 | 1 / 0 | |
| 4.29.0 | 1 / 0 | |
| 4.28.6 | 1 / 0 | |
| 4.28.5 | 1 / 0 | |
| 4.28.4 | 1 / 0 | |
| 4.28.3 | 1 / 0 | |
| 4.28.2 | 1 / 0 | |
| 4.28.1 | 1 / 0 | |
| 4.28.0 | 1 / 0 | |
| 4.27.3 | 1 / 0 | |
| 4.27.2 | 1 / 0 | |
| 4.27.1 | 1 / 0 | |
| 4.27.0 | 1 / 0 | |
| 4.26.2 | 1 / 0 | |
| 4.26.1 | 1 / 0 | |
| 4.26.0 | 1 / 0 | |
| 4.25.3 | 1 / 0 | |
| 4.25.2 | 1 / 0 | |
| 4.25.1 | 1 / 0 | |
| 4.25.0 | 1 / 0 | |
| 4.24.0 | 1 / 0 | |
| 4.23.4 | 1 / 0 | |
| 4.23.3 | 1 / 0 | |
| 4.23.2 | 1 / 0 | |
| 4.23.1 | 1 / 0 | |
| 4.23.0 | 1 / 0 | |
| 4.22.1 | 1 / 0 | |
| 4.22.0 | 1 / 0 | |
| 4.21.6 | 1 / 0 | |
| 4.21.5 | 1 / 0 | |
| 4.21.4 | 1 / 0 | |
| 4.21.3 | 1 / 0 | |
| 4.21.2 | 1 / 0 | |
| 4.21.1 | 1 / 0 | |
| 4.21.0 | 1 / 0 | |
| 4.20.2 | 1 / 0 | |
| 4.20.1 | 1 / 0 | |
| 4.20.0 | 1 / 0 | |
| 4.19.1 | 1 / 0 | |
| 4.19.0 | 1 / 0 | |
| 4.18.9 | 1 / 0 | |
| 4.18.8 | 1 / 0 | |
| 4.18.7 | 1 / 0 | |
| 4.18.6 | 1 / 0 | |
| 4.18.5 | 1 / 0 | |
| 4.18.4 | 1 / 0 | |
| 4.18.3 | 1 / 0 | |
| 4.18.2 | 1 / 0 | |
| 4.18.1 | 1 / 0 | |
| 4.18.0 | 1 / 0 | |
| 4.17.10 | 1 / 0 | |
| 4.17.9 | 1 / 0 | |
| 4.17.8 | 1 / 0 | |
| 4.17.7 | 1 / 0 | |
| 4.17.6 | 1 / 0 | |
| 4.17.5 | 1 / 0 | |
| 4.17.4 | 1 / 0 | |
| 4.17.3 | 1 / 0 | |
| 4.17.2 | 1 / 0 | |
| 4.17.1 | 1 / 0 | |
| 4.17.0 | 1 / 0 | |
| 4.16.7 | 1 / 0 | |
| 4.16.6 | 1 / 0 | |
| 4.16.5 | 1 / 0 | |
| 4.16.4 | 1 / 0 | |
| 4.16.3 | 1 / 0 | |
| 4.16.2 | 1 / 0 | |
| 4.16.1 | 1 / 0 | |
| 4.16.0 | 1 / 0 | |
| 4.15.2 | 1 / 0 | |
| 4.15.1 | 1 / 0 | |
| 4.15.0 | 1 / 0 | |
| 4.14.6 | 1 / 0 | |
| 4.14.5 | 1 / 0 | |
| 4.14.4 | 1 / 0 | |
| 4.14.3 | 1 / 0 | |
| 4.14.2 | 1 / 0 | |
| 4.14.1 | 1 / 0 | |
| 4.14.0 | 1 / 0 | |
| 4.13.10 | 1 / 0 | |
| 4.13.9 | 1 / 0 | |
| 4.13.8 | 1 / 0 | |
| 4.13.7 | 1 / 0 | |
| 4.13.6 | 1 / 0 | |
| 4.13.5 | 1 / 0 | |
| 4.13.4 | 0 / 0 | |
| 4.13.3 | 0 / 0 | |
| 4.13.2 | 0 / 0 | |
| 4.13.1 | 0 / 0 | |
| 4.13.0 | 0 / 0 | |
| 4.12.1 | 0 / 0 | |
| 4.12.0 | 0 / 0 | |
| 4.11.3 | 0 / 0 | |
| 4.11.2 | 0 / 0 | |
| 4.11.1 | 0 / 0 |
v4.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.29.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.29.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.29.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.18.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.