@verdaccio/e2e-cli
CLI tool to run Verdaccio e2e tests against any running registry
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Verdaccio org uses GitHub Actions CI publishing with SLSA attestation; publisher=GitHub Actions is expected for this package. | ai | |
| phantom-deps | phantom-dep:get-port | AI (phantom-deps): get-port is referenced in config files per the finding; stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.9.0 | 4 / 4 | |
| 2.4.0 | 3 / 4 | |
| 2.3.0 | 4 / 4 | |
| 2.2.0 | 4 / 4 | |
| 2.1.1 | 4 / 4 |
v2.9.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-24. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.