← Home

@npmcli/node-gyp

npm Repository Homepage

Tools for dealing with node-gyp packages

9
Versions
ISC
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

saquibkhannpm-cli-opsreggiowlstronaut

Keywords

npmclinode-gyp

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from bonkydog (original author) to isaacs reflects legitimate transfer to the @npmcli org team; isaacs is a well-known npm core maintainer with a strong track record. ai

Versions (showing 9 of 9)

Version Deps Published
6.0.0 0 / 3
5.0.0 0 / 3
4.0.0 0 / 3
3.0.0 0 / 3
2.0.0 0 / 3
1.0.3 0 / 3
1.0.2 0 / 3
1.0.1 0 / 2
1.0.0 0 / 2

v6.0.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.0.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.0.0

2 findings
HIGH Publisher changed: bonkydog → lukekarrys (on 2022-10-14) provenance

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

v2.0.0

2 findings
HIGH Publisher changed: bonkydog → gar (on 2022-04-05) provenance

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

v1.0.3

2 findings
HIGH Publisher changed: bonkydog → gar (on 2021-10-04) provenance

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

v1.0.2

2 findings
HIGH Publisher changed: bonkydog → isaacs (on 2021-02-09) provenance

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

v1.0.1

2 findings
HIGH Publisher changed: bonkydog → isaacs (on 2020-10-02) provenance

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

v1.0.0

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.