@react-spectrum/codemods
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a declared runtime dep used by the CLI; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:ts-node | AI (phantom-deps): ts-node is a declared dep used for TypeScript execution; stable false positive for this CLI package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Framework-scoped type package; convention-loaded, stable false positive. | ai | |
| phantom-deps | phantom-dep:@react-types/shared | AI (phantom-deps): First-party Adobe types package; referenced via config, stable false positive for this monorepo package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.2.2 | 14 / 4 | |
| 1.2.1 | 14 / 2 | |
| 1.2.0 | 14 / 2 | |
| 1.1.0 | 13 / 2 | |
| 1.0.1 | 13 / 2 | |
| 1.0.0 | 13 / 2 |
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.