@flowrag/storage-opensearch
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): Transition from manual (zweer) to GitHub Actions publishing is confirmed by SLSA provenance attestation; expected for this package. | ai | |
| phantom-deps | phantom-dep:@flowrag/core | AI (phantom-deps): Same-org scoped dependency in monorepo; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@opensearch-project/opensearch | AI (phantom-deps): Config-referenced library; phantom-dep heuristic false positive for this pattern. | ai | |
| dependencies | unvetted-dep:@flowrag/core | AI (dependencies): Same-monorepo sibling dependency; expected for @flowrag/* scoped packages. | ai |
v0.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-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.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.