← Home

libnpmexec

npm Repository Homepage

npm exec (npx) programmatic API

96
Versions
ISC
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

saquibkhannpm-cli-opsreggiowlstronaut

Keywords

npmnpmclilibnpmcliworkspaceslibnpmexec

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Publish environment variation within the npm CLI team; gitHead presence is not guaranteed across all publish flows. ai
provenance no-provenance AI (provenance): Informational finding; npm CLI workspace packages may not yet have Sigstore provenance enabled. Not a security risk. ai
provenance publisher-changed AI (provenance): reggi is a known npm CLI team member; publisher change from gar to reggi is a legitimate maintainer rotation within the npm org. ai
publish-pattern new-deps-added AI (publish-pattern): @npmcli/package-json is an official @npmcli-scoped package, consistent with the existing dependency tree. ai

Versions (showing 96 of 96)

Version Deps Published
10.2.9 12 / 8
10.2.8 12 / 8
10.2.7 12 / 8
10.2.6 12 / 8
10.2.4 12 / 8
10.2.3 12 / 8
10.2.2 12 / 8
10.2.1 12 / 8
10.2.0 12 / 8
10.1.12 12 / 8
10.1.11 12 / 8
10.1.10 12 / 8
10.1.9 12 / 8
10.1.8 12 / 8
10.1.7 12 / 8
10.1.6 11 / 8
10.1.5 11 / 8
10.1.4 11 / 8
10.1.3 11 / 8
10.1.2 11 / 8
10.1.1 11 / 8
10.1.0 11 / 8
10.0.0 10 / 8
9.0.5 10 / 8
9.0.4 10 / 8
9.0.3 10 / 8
9.0.2 10 / 8
9.0.1 10 / 8
9.0.0 10 / 8
8.1.4 10 / 8
8.1.3 10 / 8
8.1.2 10 / 8
8.1.1 10 / 8
8.1.0 10 / 8
8.0.0 10 / 8
7.0.10 11 / 8
7.0.9 11 / 8
7.0.8 11 / 8
7.0.7 11 / 8
7.0.6 11 / 8
7.0.5 11 / 8
7.0.4 11 / 8
7.0.3 11 / 8
7.0.2 11 / 8
7.0.1 11 / 8
7.0.0 11 / 8
6.0.5 11 / 8
6.0.4 11 / 8
6.0.3 11 / 8
6.0.2 11 / 8
6.0.1 11 / 8
6.0.0 11 / 9
5.0.17 12 / 8
5.0.16 12 / 8
5.0.15 12 / 8
5.0.14 12 / 8
5.0.13 12 / 8
5.0.12 12 / 8
5.0.11 12 / 8
5.0.10 12 / 8
5.0.9 12 / 9
5.0.8 12 / 9
5.0.7 12 / 9
5.0.6 12 / 9
5.0.5 12 / 9
5.0.4 12 / 6
5.0.3 12 / 6
5.0.2 12 / 6
5.0.1 12 / 6
5.0.0 12 / 6
4.0.14 14 / 6
4.0.13 14 / 6
4.0.12 14 / 6
4.0.11 14 / 4
4.0.10 14 / 4
4.0.9 14 / 4
4.0.8 12 / 4
4.0.7 12 / 4
4.0.6 12 / 4
4.0.5 12 / 4
4.0.4 12 / 4
4.0.3 12 / 4
4.0.2 12 / 3
4.0.1 12 / 3
4.0.0 12 / 3
3.0.3 11 / 3
3.0.2 11 / 2
3.0.1 11 / 7
3.0.0 11 / 7
2.0.1 11 / 7
2.0.0 11 / 7
1.2.0 11 / 7
1.1.1 11 / 7
1.1.0 11 / 7
1.0.1 10 / 7
1.0.0 10 / 7

v10.2.9

1 finding
INFO No provenance attestation provenance

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

v10.2.8

1 finding
INFO No provenance attestation provenance

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

v10.2.7

1 finding
INFO No provenance attestation provenance

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

v10.2.6

1 finding
LOW No provenance attestation provenance

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

v10.2.4

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

HIGH Publisher changed: owlstronaut → gar (on 2026-03-11) provenance

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

v10.2.3

1 finding
LOW No provenance attestation provenance

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

v10.2.2

2 findings
HIGH Publisher changed: reggi → owlstronaut (on 2026-02-19) provenance

This version was published by a different npm account than previous versions on 2026-02-19. 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.

v10.2.1

2 findings
HIGH Publisher changed: gar → reggi (on 2026-02-11) provenance

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

v10.2.0

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

HIGH Publisher changed: owlstronaut → gar (on 2026-02-04) provenance

This version was published by a different npm account than previous versions on 2026-02-04. 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.

v10.1.12

1 finding
LOW No provenance attestation provenance

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

v10.1.11

1 finding
LOW No provenance attestation provenance

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

v10.1.10

1 finding
LOW No provenance attestation provenance

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

v10.1.9

1 finding
LOW No provenance attestation provenance

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

v10.1.8

1 finding
LOW No provenance attestation provenance

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

v10.1.7

1 finding
LOW No provenance attestation provenance

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

v10.1.6

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: reggi → owlstronaut (on 2025-09-03) provenance

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

v10.1.5

2 findings
HIGH Publisher changed: gar → reggi (on 2025-07-24) provenance

This version was published by a different npm account than previous versions on 2025-07-24. 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.

v10.1.4

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

LOW No provenance attestation provenance

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

INFO Publisher changed: owlstronaut → gar (on 2025-06-12) provenance

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

v10.1.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: gar → owlstronaut (on 2025-05-21) provenance

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

v10.1.2

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

LOW No provenance attestation provenance

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

INFO Publisher changed: owlstronaut → gar (on 2025-05-15) provenance

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

v10.1.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: gar → owlstronaut (on 2025-04-08) provenance

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

v10.1.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

LOW No provenance attestation provenance

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

v10.0.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

LOW No provenance attestation provenance

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

v9.0.5

1 finding
LOW No provenance attestation provenance

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

v9.0.4

1 finding
LOW No provenance attestation provenance

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

v9.0.3

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

HIGH Publisher changed: owlstronaut → gar (on 2026-03-11) provenance

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

v9.0.2

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

HIGH Publisher changed: owlstronaut → gar (on 2026-03-04) provenance

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

v9.0.1

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 Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

v9.0.0

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 Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

v8.1.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 Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

v8.1.3

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 Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

v8.1.2

3 findings
INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

INFO Publisher changed: lukekarrys → gar (on 2024-05-29) provenance

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

v8.1.1

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: gar → lukekarrys (on 2024-05-15) provenance

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

v8.1.0

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 Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

v8.0.0

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 Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.