vite-plugin-rnw
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/babel__core | AI (phantom-deps): Framework-scoped type package; loaded by convention in Babel-based build tools. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-modules-commonjs | AI (phantom-deps): Babel plugin loaded by convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-react-jsx-source | AI (phantom-deps): Babel plugin loaded by convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:react-refresh | AI (phantom-deps): react-refresh is loaded by convention in dev tooling; stable pattern for vite plugins. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-react-jsx-self | AI (phantom-deps): Babel plugin loaded by convention; stable for this package. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): No code changes vs prior version; rapid publish likely a version bump/fix, not malicious automation. | ai | |
| provenance | missing-githead | AI (provenance): Trusted publisher with long track record; missing gitHead is a minor CI environment change, not a malware indicator. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.0.11 | 5 / 3 | |
| 0.0.10 | 5 / 2 | |
| 0.0.9 | 5 / 2 | |
| 0.0.8 | 5 / 2 | |
| 0.0.7 | 10 / 7 | |
| 0.0.6 | 10 / 7 | |
| 0.0.5 | 10 / 7 | |
| 0.0.4 | 8 / 7 | |
| 0.0.3 | 8 / 7 | |
| 0.0.2 | 8 / 7 | |
| 0.0.1 | 8 / 7 |
v0.0.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dannyhw.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dannyhw.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.