@canopytax/set-registry-key
Native node module that adds registry keys on windows. Written in C++. That's all.
1
Versions
—
License
Yes
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
alizenguyenparkmron.douglasmiracastillogeoctrltannerrigbyrchilds
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): The install script value is empty string; node-gyp rebuild is only in the build script, not executed at install time. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Native addon package; bundled .node binaries are expected for a node-gyp-based Windows registry binding. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped org package (@canopytax) with 895-day history; missing metadata is cosmetic, not indicative of spam. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.0.5 | 0 / 0 |
v0.0.5
3 findings
HIGH
Package has 'install' script
install-scripts
Script: node-gyp rebuild
HIGH
Bundled binary files (2)
npm-metadata
Package contains compiled binaries that could be backdoors: • build/Release/native.node • bin/darwin-arm64-119/set-registry-key.node
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.