verdaccio
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 migrated to GitHub Actions CI publishing with SLSA provenance; this is the expected publisher going forward. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): verdacciopack addition is consistent with the project's org-level CI publishing transition. | ai | |
| phantom-deps | phantom-dep:@verdaccio/ui-theme | AI (phantom-deps): Config-referenced plugin/theme; not directly imported by design in verdaccio's architecture. | ai | |
| phantom-deps | phantom-dep:@verdaccio/package-filter | AI (phantom-deps): First-party monorepo sub-package used via config/dynamic loading; stable false positive. | ai | |
| phantom-deps | phantom-dep:verdaccio-audit | AI (phantom-deps): Runtime plugin loaded via config, not static import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:lru-cache | AI (phantom-deps): Likely used transitively or in build output; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:verdaccio-htpasswd | AI (phantom-deps): Runtime plugin loaded via config, not static import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@verdaccio/signature | AI (phantom-deps): First-party monorepo sub-package used via config/dynamic loading; stable false positive. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 6.7.2 | 31 / 50 | |
| 6.7.1 | 31 / 50 | |
| 6.7.0 | 31 / 50 | |
| 6.6.2 | 31 / 50 | |
| 6.6.0 | 31 / 48 | |
| 6.5.2 | 31 / 52 | |
| 6.5.1 | 31 / 52 | |
| 6.5.0 | 31 / 50 | |
| 6.4.0 | 31 / 50 | |
| 6.3.2 | 30 / 49 | |
| 6.3.1 | 30 / 49 | |
| 6.3.0 | 30 / 49 | |
| 6.2.9 | 30 / 44 | |
| 6.2.8 | 30 / 44 | |
| 6.2.7 | 30 / 44 | |
| 6.2.5 | 30 / 44 | |
| 6.2.4 | 30 / 44 | |
| 6.2.3 | 30 / 44 | |
| 6.2.2 | 30 / 44 | |
| 6.2.1 | 30 / 44 | |
| 6.2.0 | 30 / 44 | |
| 6.1.6 | 32 / 74 | |
| 6.1.5 | 32 / 74 | |
| 6.1.4 | 32 / 74 | |
| 6.1.3 | 32 / 74 |
v6.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.7.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-16. 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.
v6.7.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-16. 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.
v6.6.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-14. 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.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.