← Home

libnpmhook

npm Repository Homepage

programmatic API for managing npm registry hooks

32
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

hashtagchrisregginpm-cli-opssaquibkhanfritzygar

Keywords

npmhooksregistrynpm api

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): gar is a long-standing npm CLI team member; publisher rotation within the npm org is expected. ai
provenance missing-githead AI (provenance): Publish environment change within the npm CLI team; no security concern. ai
maintainer-change maintainer-added AI (maintainer-change): hashtagchris and reggi are known npm/GitHub team members; routine team roster update. ai
maintainer-change maintainer-removed AI (maintainer-change): lukekarrys removal is consistent with npm CLI team roster changes. ai

Versions (showing 32 of 32)

Version Deps Published
11.0.0 2 / 4
10.0.5 2 / 4
10.0.4 2 / 4
10.0.3 2 / 4
10.0.2 2 / 4
10.0.1 2 / 4
10.0.0 2 / 4
9.0.4 2 / 4
9.0.3 2 / 4
9.0.1 2 / 4
9.0.0 2 / 4
8.0.4 2 / 4
8.0.3 2 / 4
8.0.2 2 / 3
8.0.1 2 / 3
8.0.0 2 / 3
7.0.1 2 / 3
7.0.0 2 / 2
6.0.3 2 / 4
6.0.2 2 / 4
6.0.1 2 / 4
6.0.0 2 / 4
5.0.3 4 / 6
5.0.2 4 / 6
5.0.1 5 / 6
5.0.0 4 / 7
4.0.1 2 / 6
4.0.0 2 / 6
3.0.1 2 / 6
3.0.0 2 / 6
2.0.1 2 / 6
2.0.0 2 / 6

v11.0.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: lukekarrys → gar (on 2024-10-03) provenance

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

1 finding
LOW No provenance attestation provenance

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

v10.0.4

2 findings
LOW No provenance attestation provenance

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.

v10.0.3

3 findings
LOW No provenance attestation provenance

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-04-25) provenance

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

v10.0.2

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 → lukekarrys (on 2024-04-03) provenance

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

v10.0.1

3 findings
LOW No provenance attestation provenance

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 2023-12-06) provenance

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

v10.0.0

1 finding
LOW No provenance attestation provenance

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