@verdaccio/search-indexer
3
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
privatepackagerepositoryregistryenterprisemodulesproxyserververdaccio
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 publishing to GitHub Actions CI with SLSA attestation; this is the expected new publisher for all future versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): verdacciopack is the org-level npm account for the verdaccio project; addition is consistent with the CI/CD migration. | ai |
v8.0.2
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.
v8.0.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
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.