@zephyr3d/device
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/node | AI (phantom-deps): Type-only package; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@webgpu/types | AI (phantom-deps): Type-only package; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@rollup/plugin-commonjs | AI (phantom-deps): Build tool referenced in config; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:rollup-plugin-import-css | AI (phantom-deps): Build tool referenced in config; phantom-dep false positive for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.2.9 | 5 / 27 | |
| 0.2.8 | 5 / 27 | |
| 0.2.7 | 5 / 27 | |
| 0.2.5 | 5 / 27 |
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.