← Home

shell-quote

npm Repository Homepage

quote and parse shell commands

9
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

goto-bus-stopkarissaljharbjiwaddell

Keywords

commandparsequoteshell

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transition from substack to goto-bus-stop, a well-established npm publisher with strong track record. ai
maintainer-change maintainer-added AI (maintainer-change): Known community takeover of substack packages; goto-bus-stop is a trusted publisher with 1242 approved packages. ai
dependencies unvetted-dep:array-map AI (dependencies): array-map is a long-standing, stable polyfill dependency of this package with no material risk; finding is a stable false positive for shell-quote. ai
dependencies unvetted-dep:array-reduce AI (dependencies): array-reduce is a long-standing, stable polyfill dependency of this package with no material risk; finding is a stable false positive for shell-quote. ai
provenance no-provenance AI (provenance): shell-quote is a well-established package published by a trusted maintainer; lack of Sigstore provenance is expected for this publishing style and does not indicate risk. ai

Versions (showing 9 of 9)

Version Deps Published
1.8.4 0 / 10
1.8.3 0 / 11
1.8.2 0 / 11
1.8.1 0 / 10
1.8.0 0 / 10
1.7.4 0 / 8
1.7.3 0 / 1
1.6.2 0 / 1
1.6.1 4 / 1

v1.8.4

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

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.8.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.8.0

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

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: substack → ljharb (on 2022-10-13) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-10-13. This could indicate a legitimate maintainer transition or an account compromise.

v1.7.3

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

2 findings
HIGH Publisher changed: substack → goto-bus-stop (on 2019-08-13) provenance

This version was published by a different npm account than previous versions on 2019-08-13. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v1.6.1

1 finding
LOW No provenance attestation provenance

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