@dysonic/dy-cli-cmd-build
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:esbuild | AI (phantom-deps): Known implicit binary dep; phantom-dep heuristic false positive for build tools. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit runtime dep; stable false positive for this package type. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Referenced in config files; phantom-dep heuristic false positive for build tooling. | ai | |
| phantom-deps | phantom-dep:less | AI (phantom-deps): Referenced in config files; stable false positive for this build package. | ai | |
| phantom-deps | phantom-dep:rollup-plugin-esbuild | AI (phantom-deps): Referenced in config files; stable false positive for this build package. | ai | |
| phantom-deps | phantom-dep:rollup-plugin-postcss | AI (phantom-deps): Referenced in config files; stable false positive for this build package. | ai | |
| phantom-deps | phantom-dep:less-plugin-npm-import | AI (phantom-deps): Referenced in config files; stable false positive for this build package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.0.8 | 20 / 2 | |
| 1.0.7 | 20 / 2 | |
| 1.0.6 | 20 / 2 | |
| 1.0.2 | 21 / 2 |
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.