zeromq
3
Versions
—
License
Yes
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
rgbkrkronkorvingrolftimmermansminrktjholowaychukcaptainsafialgeigerzeromqjs-integrationaminya
Keywords
zeromqzmq0mqømqlibzmqzmtpmessagemessagingqueueasyncsocketsnativebindingaddonnapi
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:node-gyp | AI (phantom-deps): Known implicit build dependency for native module. | ai | |
| dependencies | unvetted-dep:@aminya/node-gyp-build | AI (dependencies): Maintainer's own fork of node-gyp-build for prebuild fetching; consistent with native binding pattern. | ai | |
| phantom-deps | phantom-dep:cross-env | AI (phantom-deps): Used in install/build scripts, not imported directly; expected for config tooling. | ai | |
| 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 | |
| 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 | |
| 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 |
v6.0.7
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.
v6.0.3
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.