@vertesia/react
React helpers for Composable AI
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:json-schema | AI (phantom-deps): json-schema is a declared runtime dependency in this package; phantom-dep fires spuriously here. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 1.4.1 | 2 / 3 | |
| 1.4.0 | 2 / 3 | |
| 1.3.0 | 2 / 5 | |
| 1.2.0 | 2 / 5 | |
| 1.1.0 | 2 / 5 | |
| 1.0.0 | 2 / 5 | |
| 0.82.4 | 3 / 3 | |
| 0.81.1 | 3 / 3 | |
| 0.80.0 | 3 / 3 | |
| 0.79.4 | 3 / 3 | |
| 0.79.3 | 3 / 3 | |
| 0.79.2 | 3 / 3 | |
| 0.79.1 | 3 / 3 | |
| 0.78.0 | 3 / 3 | |
| 0.77.0 | 3 / 3 | |
| 0.76.0 | 3 / 3 | |
| 0.74.0 | 3 / 3 | |
| 0.73.0 | 3 / 3 | |
| 0.72.0 | 3 / 3 | |
| 0.71.0 | 3 / 3 | |
| 0.70.0 | 3 / 3 | |
| 0.68.0 | 3 / 3 | |
| 0.67.0 | 3 / 3 | |
| 0.66.0 | 3 / 3 | |
| 0.65.0 | 3 / 3 | |
| 0.64.0 | 3 / 3 | |
| 0.63.0 | 3 / 3 | |
| 0.62.0 | 3 / 3 | |
| 0.61.0 | 3 / 3 | |
| 0.60.0 | 3 / 3 | |
| 0.59.0 | 3 / 3 | |
| 0.58.0 | 3 / 3 | |
| 0.57.0 | 3 / 3 | |
| 0.56.0 | 4 / 2 | |
| 0.55.0 | 4 / 2 | |
| 0.54.0 | 4 / 2 | |
| 0.52.0 | 4 / 2 | |
| 0.51.0 | 4 / 2 | |
| 0.50.1 | 4 / 2 | |
| 0.50.0 | 4 / 2 | |
| 0.49.0 | 4 / 2 | |
| 0.48.0 | 4 / 2 | |
| 0.47.0 | 4 / 2 | |
| 0.46.0 | 4 / 2 | |
| 0.45.3 | 4 / 2 | |
| 0.45.2 | 4 / 2 | |
| 0.45.1 | 4 / 2 | |
| 0.45.0 | 4 / 2 | |
| 0.44.0 | 4 / 2 | |
| 0.43.0 | 4 / 2 | |
| 0.42.2 | 4 / 2 |
v1.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.