@jsenv/plugin-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 — 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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Long-lived jsenv ecosystem package; missing description is a stable cosmetic gap, not a malware signal. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-react-jsx | AI (phantom-deps): Babel plugin loaded by convention in jsenv React plugin; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-react-jsx-source | AI (phantom-deps): Same as above — convention-loaded Babel plugin. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-react-jsx-development | AI (phantom-deps): Same as above — convention-loaded Babel plugin. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.7.37 | 8 / 8 | |
| 1.7.35 | 8 / 8 | |
| 1.7.32 | 8 / 8 | |
| 1.7.30 | 8 / 8 | |
| 1.7.28 | 8 / 8 | |
| 1.7.27 | 8 / 8 | |
| 1.7.25 | 8 / 8 | |
| 1.7.22 | 8 / 8 | |
| 1.7.21 | 8 / 8 | |
| 1.7.20 | 8 / 8 |
v1.7.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.