zeromq
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:install | AI (install-scripts): Native addon; install script selects prebuilt binaries or compiles via cmake-ts — standard pattern for this package. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt .node binaries for multiple platforms are the documented distribution mechanism for this native binding. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in install script to invoke cmake-ts build tool; expected for native addon compilation. | ai | |
| phantom-deps | phantom-dep:node-addon-api | AI (phantom-deps): node-addon-api is a C++ header-only dep referenced in cmake-ts config, not imported in JS — stable false positive. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 6.5.0 | 2 / 44 |
v6.5.0
3 findingsScript: node ./script/install.js
Package contains compiled binaries that could be backdoors: • build/darwin/arm64/node/libc-115-Release/addon.node • build/darwin/x64/node/libc-115-Release/addon.node • build/darwin/x64/node/libc-72-Release/addon.node • build/linux/arm64/node/glibc-127-Release/addon.node • build/linux/arm64/node/musl-127-Release/addon.node • build/linux/x64/node/glibc-115-Release/addon.node • build/linux/x64/node/glibc-127-Release/addon.node • build/linux/x64/node/glibc-72-Release/addon.node • build/linux/x64/node/musl-127-Release/addon.node • build/win32/arm64/node/msvc-115-Release/addon.node ... and 4 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.