← Home

@memberjunction/ai-knowledge-search

MemberJunction: Unified Search Service - vector + full-text + RRF fusion

4
Versions
ISC
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

craig.adam.bcethan-bcjordanfanapourcaeleb.balanesiianzygmuntanag123hiltongrrkihm-bc

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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

Versions (showing 4 of 4)

Version Deps Published
5.24.0 8 / 2
5.23.0 8 / 2
5.22.0 8 / 2
0.0.1 0 / 0

v5.24.0

1 finding
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.

v5.23.0

2 findings
HIGH Publisher changed: caeleb.balanesi → GitHub Actions (on 2026-04-04) provenance

This 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.

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.

v5.22.0

2 findings
HIGH Publisher changed: caeleb.balanesi → GitHub Actions (on 2026-04-02) provenance

This 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.

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.

v0.0.1

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.