node-gyp-build-optional-packages MIT 19 versions

node-gyp-build-optional-packages

npm Repository Homepage

Build tool and bindings loader for node-gyp that supports prebuilds

19

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

kriszyp

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:detect-libc	AI (dependencies): detect-libc is a well-known legitimate package for detecting Linux C library; appropriate dependency for a native bindings loader.	ai	2026/04/23
semgrep	semgrep:child-process-import	AI (semgrep): child_process is required for a native bindings build tool to invoke node-gyp and test binaries; stable and expected for this package.	ai	2026/04/23
semgrep	semgrep:child-process-exec	AI (semgrep): exec() is used to invoke the package's own test binary; legitimate and expected for a build tool.	ai	2026/04/23
semgrep	semgrep:child-process-spawn	AI (semgrep): spawn() is used to run node-gyp build commands; core functionality of a native bindings build tool.	ai	2026/04/23
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require is used only to load package.json via path.join(cwd, 'package.json'); standard and safe pattern.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): Package is a legitimate, widely-used native bindings build tool with 13.7M weekly downloads; bogus-package signals are false positives here.	ai	2026/04/23

Versions (showing 19 of 19)

Version	Deps	Published
5.2.2	1 / 3	2024-06-09
5.2.1	1 / 3	2024-06-09
5.2.0	1 / 3	2024-06-08
5.1.1	1 / 3	2023-07-28
5.1.0	1 / 3	2023-05-09
5.0.7	0 / 3	2023-01-30
5.0.6	0 / 3	2023-01-20
5.0.5	0 / 3	2022-12-02
5.0.4	0 / 3	2022-11-28
5.0.3	0 / 3	2022-05-29
5.0.2	0 / 3	2022-05-18
5.0.1	0 / 3	2022-05-17
5.0.0	0 / 3	2022-05-14
4.3.5	0 / 3	2022-05-29
4.3.4	0 / 3	2022-05-28
4.3.3	0 / 3	2022-05-28
4.3.2	0 / 3	2022-04-09
4.3.1	0 / 3	2022-04-06
4.3.0	0 / 3	2022-04-05

v5.2.2

1 finding

LOW No provenance attestation provenance

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

v5.2.1

1 finding

LOW No provenance attestation provenance

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

v5.2.0

1 finding

LOW No provenance attestation provenance

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

v5.1.1

1 finding

LOW No provenance attestation provenance

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

v5.1.0

1 finding

LOW No provenance attestation provenance

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

v5.0.7

1 finding

LOW No provenance attestation provenance

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

v5.0.6

1 finding

LOW No provenance attestation provenance

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

v5.0.5

1 finding

LOW No provenance attestation provenance

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

v5.0.4

1 finding

LOW No provenance attestation provenance

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

v5.0.3

1 finding

LOW No provenance attestation provenance

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

v5.0.2

1 finding

LOW No provenance attestation provenance

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

v5.0.1

1 finding

LOW No provenance attestation provenance

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

v5.0.0

1 finding

LOW No provenance attestation provenance

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

v4.3.5

1 finding

LOW No provenance attestation provenance

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

v4.3.4

1 finding

LOW No provenance attestation provenance

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

v4.3.3

1 finding

LOW No provenance attestation provenance

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

v4.3.2

1 finding

LOW No provenance attestation provenance

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

v4.3.1

1 finding

LOW No provenance attestation provenance

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

v4.3.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.