← Home

string-argv

npm Repository Homepage

string-argv parses a string into an argument array to mimic process.argv. This is useful when testing Command Line Utilities that you want to pass arguments to.

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

mccormickacellule

Keywords

argv

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from mccormicka to cellule in 2016 is consistent with a legitimate transition; devDependencies reference eslint-config-cellule confirming the relationship. Stable for this package. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainer cellule is consistent with the 2016 transition; devDependencies confirm the relationship. No malicious indicators present. ai
email-domain unclaimed-email:anthony.mccormick at gmail.com AI (email-domain): The email domain is gmail.com, a well-known provider with valid DNS. The analyzer appears to have misidentified the full email string as the domain. This is a stable false positive for this package. ai
phantom-deps phantom-dep:bunyan AI (phantom-deps): Bunyan is listed as a dependency but not directly imported; this is a minor packaging artifact in a 12-year-old version, not a security concern. ai

Versions (showing 10 of 10)

Version Deps Published
0.3.2 0 / 2
0.3.1 0 / 2
0.3.0 0 / 2
0.2.1 0 / 3
0.2.0 0 / 3
0.1.2 0 / 3
0.1.1 0 / 3
0.1.0 0 / 3
0.0.2 0 / 3
0.0.1 1 / 5

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

1 finding
LOW No provenance attestation provenance

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

v0.1.1

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

2 findings
HIGH Publisher changed: mccormicka → cellule (on 2016-03-11) provenance

This version was published by a different npm account than previous versions on 2016-03-11. 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.

v0.0.1

2 findings
HIGH Unclaimed maintainer email domain: anthony.mccormick at gmail.com email-domain

Maintainer email 'anthony.mccormick AT gmail.com' uses domain 'anthony.mccormick at gmail.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.