← Home

registry-js

A simple and opinionated library for working with the Windows registry

1
Versions
MIT
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

joshaberniikshiftkeysergiou87tidy-dev

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:install AI (install-scripts): Standard native addon install pattern (prebuild-install || node-gyp rebuild); stable for this package. ai
phantom-deps phantom-dep:node-addon-api AI (phantom-deps): node-addon-api is used implicitly by node-gyp for native addon builds; not directly imported in JS. ai
phantom-deps phantom-dep:prebuild-install AI (phantom-deps): prebuild-install is invoked via install script, not imported; known implicit binary dependency pattern. ai

Versions (showing 1 of 1)

Version Deps Published
1.16.1 2 / 11

v1.16.1

2 findings
HIGH Package has 'install' script install-scripts

Script: prebuild-install || node-gyp rebuild

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.