@valbuild/react
Val - React internal helpers
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; missing gitHead is a minor CI config change, not a supply chain risk for this package. | ai | |
| phantom-deps | phantom-dep:@valbuild/ui | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic false positive for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@valbuild/shared | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic false positive for monorepo packages. | ai | |
| phantom-deps | phantom-dep:base64-arraybuffer | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse README is typical for monorepo sub-packages; not a spam indicator for this established org. | ai |
Versions (showing 23 of 123)
| Version | Deps | Published |
|---|---|---|
| 0.60.14 | 5 / 5 | |
| 0.60.13 | 5 / 5 | |
| 0.60.12 | 5 / 5 | |
| 0.60.11 | 5 / 5 | |
| 0.60.10 | 5 / 5 | |
| 0.60.9 | 5 / 5 | |
| 0.60.8 | 5 / 5 | |
| 0.60.7 | 5 / 5 | |
| 0.60.6 | 5 / 5 | |
| 0.60.5 | 5 / 5 | |
| 0.60.4 | 5 / 5 | |
| 0.60.3 | 5 / 5 | |
| 0.60.2 | 5 / 5 | |
| 0.60.1 | 5 / 5 | |
| 0.60.0 | 5 / 5 | |
| 0.18.0 | 5 / 5 | |
| 0.17.0 | 5 / 5 | |
| 0.16.0 | 5 / 5 | |
| 0.15.0 | 5 / 5 | |
| 0.14.0 | 5 / 5 | |
| 0.13.3 | 4 / 5 | |
| 0.13.0 | 5 / 4 | |
| 0.12.0 | 5 / 4 |
v0.60.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.