@memberjunction/predictive-studio
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 manual publish to GitHub Actions CI/CD with SLSA attestation; this is a provenance improvement, not a takeover signal. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are same-version @memberjunction/* monorepo siblings plus rxjs; consistent with legitimate feature assembly package expansion. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 5.48.0 | 13 / 5 | |
| 5.47.0 | 13 / 5 | |
| 5.46.0 | 13 / 5 | |
| 5.45.1 | 13 / 5 | |
| 5.45.0 | 13 / 5 | |
| 5.44.0 | 13 / 5 | |
| 0.0.1 | 0 / 0 |
v5.48.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.47.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.46.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.45.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.45.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.44.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-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.