@handy-common-utils/dev-dependencies-common
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:tsx | AI (phantom-deps): tsx is a dev tooling dep used via config/scripts, not direct import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:eslint | AI (phantom-deps): Dev-dependencies aggregator; eslint declared for config distribution, not direct import. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): Dev-dependencies aggregator; prettier declared for config distribution, not direct import. | ai | |
| dependencies | unvetted-dep:es-check | AI (dependencies): es-check is a well-known ES compatibility tool; its use here as a dev dependency is expected and benign. | ai | |
| phantom-deps | phantom-dep:es-check | AI (phantom-deps): CLI tool referenced in scripts, not imported; expected for this dev-tooling package. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): CLI/config tool, not imported; expected for this dev-tooling package. | ai | |
| phantom-deps | phantom-dep:lint-staged | AI (phantom-deps): Git hook tool referenced in config, not imported; expected for this dev-tooling package. | ai | |
| phantom-deps | phantom-dep:shx | AI (phantom-deps): CLI tool used in prepare script, not imported; expected for this dev-tooling package. | ai | |
| phantom-deps | phantom-dep:source-map-support | AI (phantom-deps): Runtime support tool referenced in configs, not imported; expected for this dev-tooling package. | ai | |
| phantom-deps | phantom-dep:@handy-common-utils/dev-utils | AI (phantom-deps): Same-org utility package used as CLI/config tool; expected for this dev-tooling package. | ai | |
| phantom-deps | phantom-dep:npm-run-all | AI (phantom-deps): CLI tool referenced in scripts, not imported; expected for this dev-tooling package. | ai | |
| phantom-deps | phantom-dep:husky | AI (phantom-deps): Git hooks tool used via config, not imported; expected for this dev-tooling package. | ai | |
| phantom-deps | phantom-dep:ts-node | AI (phantom-deps): CLI tool referenced in scripts/configs, not imported; expected for this dev-tooling package. | ai | |
| phantom-deps | phantom-dep:wait-on | AI (phantom-deps): CLI tool referenced in scripts, not imported; expected for this dev-tooling package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.14.1 | 12 / 0 | |
| 1.14.0 | 12 / 0 | |
| 1.13.2 | 12 / 0 | |
| 1.13.1 | 12 / 0 | |
| 1.11.0 | 12 / 0 | |
| 1.10.1 | 12 / 0 | |
| 1.10.0 | 12 / 0 | |
| 1.9.4 | 12 / 0 | |
| 1.9.3 | 12 / 0 | |
| 1.9.2 | 12 / 0 | |
| 1.9.1 | 12 / 0 | |
| 1.8.0 | 12 / 0 | |
| 1.7.0 | 13 / 0 |
v1.14.1
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: james-hu.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
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: james-hu.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.