cli-kit
2
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
pkclarkcb1kenobiaxway_alasdair
Keywords
clicmdcommandlinecommand linecommand line interfacecommand-lineusageargvparseparserargumentoptionoptionsflagflagscommandcommandssubcommandshelpautocompleteterminalbashshellinteractive
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): CLI toolkit legitimately uses child_process to spawn subprocesses; expected for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Documented decode() utility for CLI argument passing; not obfuscation. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used in template engine renderer; standard pattern for CLI help/output templating. | ai |
v2.1.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.