@pinecone-database/pinecone
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from pinecone-ops to GitHub Actions CI/CD with SLSA provenance; legitimate automation change. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Major version bump after internal development period; established package with SLSA provenance. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 7.2.0 | 0 / 16 | |
| 7.1.0 | 0 / 16 | |
| 7.0.0 | 0 / 16 | |
| 6.1.4 | 0 / 16 | |
| 6.1.3 | 0 / 16 |
v7.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-31. 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.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.