args
Minimal toolkit for building CLIs
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): CLI toolkit legitimately uses spawn for subprocess execution; this is expected behavior for a CLI argument parser, not a security risk. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used to load a resolved package.json path for version display — a standard, safe pattern in CLI tools. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 5.0.3 | 4 / 7 | |
| 5.0.1 | 4 / 7 | |
| 5.0.0 | 4 / 7 | |
| 4.0.0 | 4 / 7 | |
| 3.0.8 | 5 / 7 | |
| 3.0.7 | 5 / 7 | |
| 3.0.6 | 5 / 7 | |
| 3.0.5 | 5 / 7 | |
| 3.0.4 | 5 / 7 | |
| 3.0.3 | 5 / 7 | |
| 3.0.2 | 5 / 7 | |
| 3.0.1 | 5 / 7 | |
| 3.0.0 | 5 / 7 | |
| 2.6.1 | 5 / 7 | |
| 2.6.0 | 5 / 7 | |
| 2.5.0 | 5 / 7 | |
| 2.4.2 | 4 / 7 | |
| 2.4.1 | 4 / 7 | |
| 2.4.0 | 4 / 7 | |
| 2.3.0 | 5 / 3 | |
| 2.2.4 | 5 / 3 | |
| 2.2.3 | 5 / 3 | |
| 2.2.2 | 5 / 8 | |
| 2.2.1 | 5 / 8 | |
| 2.2.0 | 5 / 8 | |
| 2.1.0 | 5 / 8 | |
| 2.0.0 | 5 / 8 | |
| 1.3.1 | 6 / 9 | |
| 1.3.0 | 6 / 9 | |
| 1.2.1 | 6 / 8 | |
| 1.2.0 | 5 / 9 | |
| 1.1.0 | 4 / 8 | |
| 1.0.2 | 4 / 6 | |
| 1.0.1 | 4 / 6 | |
| 1.0.0 | 4 / 6 | |
| 0.3.1 | 3 / 5 | |
| 0.3.0 | 3 / 5 | |
| 0.2.0 | 3 / 5 | |
| 0.1.1 | 2 / 5 | |
| 0.1.0 | 2 / 5 | |
| 0.0.3 | 2 / 0 | |
| 0.0.2 | 1 / 0 | |
| 0.0.1 | 0 / 0 |
v5.0.3
2 findingsThis version was published by a different npm account than previous versions on 2022-05-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.