@done-coding/cli-utils
cli utils
3
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
justsosu
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:pino | AI (phantom-deps): pino used via config/transport; phantom-dep heuristic expected. | ai | |
| phantom-deps | phantom-dep:signal-exit | AI (phantom-deps): signal-exit likely consumed indirectly or via config; stable FP. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Fires on a legitimate AES decipheriv call in a crypto utility; not obfuscation or payload delivery. | ai | |
| dependencies | unvetted-dep:lodash.set | AI (dependencies): lodash.set is a well-known utility; stable dependency across versions of this package. | ai |
v0.9.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.8
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.