get-registry
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
shigma
Keywords
registrypackagemanager
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): get-registry legitimately uses child_process to query package manager CLI tools (npm, yarn, pnpm) for their registry config. This is core to the package's purpose and not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Lack of Sigstore provenance is common and not a risk indicator for this well-established utility package with a matching public GitHub repo. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 1 / 3 |