← Home

@verdaccio/streams

5
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

sergiohgzverdaccio.npmjotadeveloperverdacciopack

Keywords

verdacciostreams

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 findings
HIGH Publisher changed: verdaccio.npm → GitHub Actions (on 2026-05-25) provenance

This 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.

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.

v10.2.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.2.1

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.