@verdaccio/streams
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Verdaccio monorepo publishes via GitHub Actions CI/CD; this transition is expected and backed by SLSA provenance. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): verdacciopack addition aligns with the official Verdaccio org's CI publishing setup. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 10.2.5 | 0 / 4 | |
| 10.2.4 | 0 / 4 | |
| 10.2.3 | 0 / 4 | |
| 10.2.2 | 0 / 4 | |
| 10.2.1 | 0 / 1 |
v10.2.5
2 findingsThis version was published by a different npm account than previous versions on 2026-05-25. 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.
v10.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.