node-gyp-build
Build tool and bindings loader for node-gyp that supports prebuilds
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Core functionality: bin.js invokes node-gyp build toolchain; expected and documented. | ai | |
| semgrep | semgrep:child-process-exec | AI (semgrep): Runs node-gyp-build-test as part of build verification; expected behavior. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): Spawns build commands; core to native addon build toolchain. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads package.json from cwd to read package name; standard pattern for build tools. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 4.8.4 | 0 / 3 | |
| 4.8.3 | 0 / 3 | |
| 4.8.2 | 0 / 3 | |
| 4.8.1 | 0 / 3 | |
| 4.8.0 | 0 / 3 | |
| 4.7.1 | 0 / 3 | |
| 4.7.0 | 0 / 3 | |
| 4.6.1 | 0 / 3 | |
| 4.6.0 | 0 / 3 | |
| 4.5.0 | 0 / 3 | |
| 4.4.0 | 0 / 3 | |
| 4.3.0 | 0 / 3 | |
| 4.2.3 | 0 / 3 | |
| 4.2.2 | 0 / 3 | |
| 4.2.1 | 0 / 3 | |
| 4.2.0 | 0 / 3 | |
| 4.1.1 | 0 / 3 | |
| 4.1.0 | 0 / 3 | |
| 4.0.0 | 0 / 3 |
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mafintosh) than the most recent previously approved version (vweevers) on 2023-08-25, but mafintosh is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.6.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mafintosh) than the most recent previously approved version (vweevers) on 2023-01-05, but mafintosh is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.5.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vweevers) than the most recent previously approved version (mafintosh) on 2022-07-01, but vweevers is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vweevers) than the most recent previously approved version (mafintosh) on 2021-09-12, but vweevers is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vweevers) than the most recent previously approved version (mafintosh) on 2020-04-25, but vweevers is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.2.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mafintosh) than the most recent previously approved version (vweevers) on 2020-03-04, but mafintosh is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mafintosh) than the most recent previously approved version (vweevers) on 2019-11-03, but mafintosh is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mafintosh) than the most recent previously approved version (vweevers) on 2019-04-26, but mafintosh is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.