@smithers-orchestrator/react-reconciler
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@smithers-orchestrator/driver | AI (dependencies): Sibling package in the same @smithers-orchestrator monorepo scope; expected dependency relationship. | ai | |
| provenance | no-provenance | AI (provenance): New package family without provenance setup; consistent across all versions, not a malice indicator. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.22.0 | 7 / 4 | |
| 0.21.0 | 7 / 4 | |
| 0.20.4 | 7 / 4 | |
| 0.20.3 | 7 / 4 | |
| 0.20.1 | 7 / 4 | |
| 0.20.0 | 7 / 4 | |
| 0.19.0 | 7 / 4 | |
| 0.18.0 | 7 / 4 | |
| 0.17.0 | 7 / 4 | |
| 0.16.9 | 7 / 2 | |
| 0.16.8 | 7 / 2 | |
| 0.16.7 | 7 / 2 | |
| 0.16.6 | 7 / 2 | |
| 0.16.5 | 7 / 2 | |
| 0.16.4 | 7 / 2 | |
| 0.16.3 | 7 / 2 | |
| 0.16.1 | 7 / 2 | |
| 0.16.0 | 7 / 2 |
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.