argv
CLI Argument Parser
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
codenothing
Keywords
cliargvoptions
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:yargs | AI (typosquat): 'argv' is a legitimate CLI argument parser predating yargs; the name describes its function (process.argv), not an attempt to impersonate yargs. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): 'argv' is a CLI argument parser with no semantic or functional relationship to ajv; the Levenshtein match is purely coincidental. | ai | |
| provenance | no-provenance | AI (provenance): Package is ~14 years old; provenance attestation did not exist when it was published. No expectation of Sigstore provenance for packages of this age. | ai |
v0.0.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
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.