@my-react/react
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established monorepo package; provenance not used across the @my-react scope consistently. | ai | |
| dependencies | unvetted-dep:@my-react/react-jsx | AI (dependencies): Sibling package in the same @my-react monorepo; stable false positive for this package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 0.3.28 | 2 / 1 | |
| 0.3.27 | 2 / 1 | |
| 0.3.26 | 2 / 1 | |
| 0.3.25 | 2 / 1 | |
| 0.3.24 | 2 / 1 | |
| 0.3.23 | 2 / 1 | |
| 0.3.22 | 2 / 1 | |
| 0.3.21 | 1 / 1 | |
| 0.3.20 | 1 / 1 | |
| 0.3.19 | 1 / 1 | |
| 0.3.18 | 1 / 1 | |
| 0.3.17 | 1 / 1 | |
| 0.3.16 | 1 / 1 | |
| 0.3.15 | 1 / 1 | |
| 0.3.14 | 1 / 1 | |
| 0.3.13 | 1 / 1 | |
| 0.3.12 | 1 / 1 | |
| 0.3.11 | 1 / 1 | |
| 0.3.10 | 1 / 1 | |
| 0.3.9 | 1 / 1 | |
| 0.3.8 | 1 / 1 | |
| 0.3.7 | 1 / 1 | |
| 0.3.6 | 1 / 1 | |
| 0.3.5 | 1 / 1 | |
| 0.3.4 | 1 / 1 | |
| 0.3.3 | 1 / 1 | |
| 0.3.2 | 1 / 1 |
v0.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.