@memberjunction/ai-knowledge-search
MemberJunction: Unified Search Service - vector + full-text + RRF fusion
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 to GitHub Actions CI/CD publisher with SLSA attestation; consistent with monorepo automation. | ai | |
| phantom-deps | phantom-dep:@memberjunction/global | AI (phantom-deps): Same-org transitive dependency in monorepo; stable pattern. | ai | |
| phantom-deps | phantom-dep:@memberjunction/aiengine | AI (phantom-deps): Same-org transitive dependency in monorepo; stable pattern. | ai | |
| phantom-deps | phantom-dep:@memberjunction/ai-vectors | AI (phantom-deps): Same-org transitive dependency in monorepo; stable pattern. | ai | |
| phantom-deps | phantom-dep:@memberjunction/core-entities | AI (phantom-deps): Same-org transitive dependency in monorepo; stable pattern. | ai |
v5.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.23.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-04. 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.
v5.22.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-02. 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.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.