@pnpm/registry-mock
3
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
No source commit
Maintainers
pnpmuserzkochan
Keywords
pnpmverdacciomockregistry
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established pnpm ecosystem package; lack of provenance is consistent across its history. | ai | |
| phantom-deps | phantom-dep:rimraf | AI (phantom-deps): Test fixture package; rimraf used in config/scripts context, not a real import concern. | ai | |
| phantom-deps | phantom-dep:verdaccio-audit | AI (phantom-deps): Registry mock; verdaccio plugins referenced in config, not imported directly by design. | ai | |
| phantom-deps | phantom-dep:verdaccio-htpasswd | AI (phantom-deps): Registry mock; verdaccio plugins referenced in config, not imported directly by design. | ai |
v6.0.0
1 finding
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.2
1 finding
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.0
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.