@better-grid/react
React adapter for Better Grid
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): No material changes from prior version; likely a CI environment shift, not a supply-chain concern. | ai |
Versions (showing 51 of 69)
| Version | Deps | Published |
|---|---|---|
| 1.0.68 | 2 / 8 | |
| 1.0.67 | 2 / 8 | |
| 1.0.66 | 2 / 8 | |
| 1.0.65 | 2 / 8 | |
| 1.0.64 | 2 / 8 | |
| 1.0.63 | 2 / 8 | |
| 1.0.62 | 2 / 8 | |
| 1.0.61 | 2 / 8 | |
| 1.0.60 | 2 / 8 | |
| 1.0.59 | 2 / 8 | |
| 1.0.58 | 2 / 8 | |
| 1.0.57 | 2 / 8 | |
| 1.0.56 | 2 / 8 | |
| 1.0.55 | 2 / 8 | |
| 1.0.54 | 2 / 8 | |
| 1.0.53 | 2 / 8 | |
| 1.0.52 | 2 / 8 | |
| 1.0.51 | 2 / 8 | |
| 1.0.50 | 2 / 8 | |
| 1.0.49 | 2 / 8 | |
| 1.0.48 | 2 / 8 | |
| 1.0.47 | 2 / 8 | |
| 1.0.46 | 2 / 8 | |
| 1.0.45 | 2 / 8 | |
| 1.0.44 | 2 / 8 | |
| 1.0.43 | 2 / 8 | |
| 1.0.42 | 2 / 8 | |
| 1.0.41 | 2 / 8 | |
| 1.0.40 | 2 / 8 | |
| 1.0.39 | 2 / 8 | |
| 1.0.38 | 2 / 8 | |
| 1.0.37 | 2 / 8 | |
| 1.0.36 | 2 / 8 | |
| 1.0.35 | 2 / 8 | |
| 1.0.34 | 2 / 8 | |
| 1.0.33 | 2 / 8 | |
| 1.0.32 | 2 / 8 | |
| 1.0.31 | 2 / 8 | |
| 1.0.30 | 2 / 8 | |
| 1.0.29 | 2 / 8 | |
| 1.0.28 | 2 / 8 | |
| 1.0.27 | 2 / 8 | |
| 1.0.26 | 2 / 8 | |
| 1.0.25 | 2 / 8 | |
| 1.0.24 | 2 / 8 | |
| 1.0.23 | 2 / 8 | |
| 1.0.22 | 2 / 8 | |
| 1.0.21 | 2 / 8 | |
| 1.0.20 | 2 / 8 | |
| 1.0.19 | 2 / 8 | |
| 1.0.18 | 2 / 8 |
v1.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.66
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jvloo.
v1.0.65
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jvloo.
v1.0.64
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jvloo.
v1.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.