← Home

cli-commands

npm Repository Homepage

A convention for building command-driven CLI apps

10
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

75lb

Keywords

command-line-commandscommand-linecommandcommandsargvparseoptionparser

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Package is 3469 days old with 10 versions; 0.0.0 is a legitimate initial release from a trusted publisher, not a throwaway malicious package. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require is an intentional plugin-loading pattern in this CLI framework; the variable is a user-supplied command module name, not an injection vector. ai
bogus-package bogus-package AI (bogus-package): Sparse metadata is typical for this publisher's early utility packages; the package has a real repo, license, and meaningful dependencies. ai

Versions (showing 10 of 10)

Version Deps Published
0.4.0 2 / 2
0.3.3 2 / 2
0.3.2 2 / 2
0.3.1 2 / 2
0.3.0 2 / 2
0.2.1 4 / 0
0.2.0 4 / 0
0.1.0 4 / 0
0.0.1 4 / 0
0.0.0 3 / 0

v0.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1

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.0.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.