← Home

@verdaccio/local-storage-legacy

npm Repository Homepage
7
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

pluginverdacciostoragelocal-storage

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Verdaccio migrated publishing to GitHub Actions CI; SLSA attestation confirms legitimate pipeline origin. ai
maintainer-change maintainer-added AI (maintainer-change): verdacciopack is the org-level npm account for the verdaccio project; consistent with official maintainer consolidation. ai
provenance no-provenance AI (provenance): Established Verdaccio project; provenance absence is consistent across their published packages. ai

Versions (showing 7 of 7)

Version Deps Published
11.3.3 9 / 8
11.3.2 9 / 8
11.3.1 9 / 8
11.3.0 9 / 8
11.2.0 8 / 8
11.1.1 8 / 5
11.1.0 8 / 5

v11.3.3

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.

v11.3.2

1 finding
INFO No provenance attestation provenance

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

v11.3.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.

v11.3.0

1 finding
INFO No provenance attestation provenance

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

v11.2.0

1 finding
INFO No provenance attestation provenance

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

v11.1.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.

v11.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.