← Home

subcommand

npm Repository Homepage

create CLI tools with subcommands

10
Versions
BSD-2-Clause
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

jhandkarissamaxogden

Keywords

minimist

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from maxogden to jhand occurred in Jan 2017 and is a long-standing, legitimate maintainer transition. jhand has a clean track record with 2 approved packages. ai
maintainer-change maintainer-added AI (maintainer-change): jhand was added as maintainer in 2017; this is a stable, historical transition with no signs of compromise. Generalizes across future versions. ai
license uncommon-license:BSD AI (license): BSD is a well-known permissive license; the uncommon-license flag is a stable false positive for this package. ai
provenance no-provenance AI (provenance): Established 11-year-old package by known author; lack of provenance is expected for packages predating Sigstore adoption and is not a security concern here. ai

Versions (showing 10 of 10)

Version Deps Published
2.1.1 3 / 2
2.1.0 4 / 2
2.0.4 4 / 2
2.0.3 4 / 2
2.0.2 4 / 2
2.0.1 4 / 2
2.0.0 4 / 2
1.1.1 4 / 2
1.1.0 4 / 2
1.0.1 3 / 1

v2.1.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.

v2.1.0

2 findings
HIGH Publisher changed: maxogden → jhand (on 2017-01-18) provenance

This version was published by a different npm account than previous versions on 2017-01-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.0.4

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.

v2.0.3

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.

v2.0.2

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.

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

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

v1.1.1

1 finding
INFO No provenance attestation provenance

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

v1.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.