node-cmake
1
Versions
—
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
cjntaylor
Keywords
cmakenativemodulebuild
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Native module loader resolves .node binary path at runtime; stable pattern for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used to invoke cmake/make build commands; core functionality of a build tool. | ai | |
| phantom-deps | phantom-dep:nan | AI (phantom-deps): nan is a native addon peer dependency referenced in config files, not imported directly in JS. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 2.5.1 | 4 / 0 |
v2.5.1
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.