@memberjunction/integration-engine
MemberJunction Integration Engine - orchestration, field mapping, and connector framework
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 publishing with SLSA attestation; consistent with monorepo automation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are pinned same-version @memberjunction/* siblings; monorepo release pattern, not third-party injection. | ai | |
| dependencies | unvetted-dep:@memberjunction/core | AI (dependencies): Sibling monorepo package pinned to same version; expected dependency pattern. | ai | |
| dependencies | unvetted-dep:@memberjunction/global | AI (dependencies): Sibling monorepo package pinned to same version; expected dependency pattern. | ai | |
| dependencies | unvetted-dep:@memberjunction/core-entities | AI (dependencies): Sibling monorepo package pinned to same version; expected dependency pattern. | ai | |
| dependencies | unvetted-dep:@memberjunction/integration-engine-base | AI (dependencies): Sibling monorepo package pinned to same version; expected dependency pattern. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 5.38.0 | 4 / 3 | |
| 5.37.0 | 4 / 3 | |
| 5.36.0 | 4 / 3 | |
| 5.35.0 | 4 / 3 | |
| 5.34.1 | 4 / 3 | |
| 5.34.0 | 4 / 3 | |
| 5.33.0 | 4 / 3 | |
| 5.32.0 | 4 / 3 | |
| 5.31.0 | 4 / 3 | |
| 5.30.1 | 4 / 3 | |
| 5.30.0 | 4 / 3 | |
| 5.29.0 | 4 / 3 | |
| 5.28.0 | 4 / 3 | |
| 5.27.1 | 4 / 3 | |
| 5.27.0 | 4 / 3 | |
| 5.26.0 | 4 / 3 | |
| 5.25.0 | 4 / 3 | |
| 5.24.0 | 4 / 3 | |
| 5.23.0 | 4 / 3 | |
| 5.22.0 | 4 / 3 | |
| 5.21.0 | 4 / 3 | |
| 5.20.0 | 4 / 3 | |
| 5.19.0 | 4 / 3 | |
| 5.18.0 | 4 / 3 | |
| 5.17.0 | 4 / 3 | |
| 5.16.0 | 4 / 3 | |
| 5.15.0 | 4 / 3 | |
| 5.14.0 | 4 / 3 | |
| 5.13.0 | 4 / 3 | |
| 5.12.0 | 4 / 3 | |
| 5.11.0 | 4 / 3 | |
| 5.10.1 | 4 / 3 | |
| 5.10.0 | 4 / 3 | |
| 5.9.0 | 4 / 3 | |
| 5.8.0 | 3 / 3 | |
| 0.0.1 | 0 / 0 |
v5.38.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.37.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.36.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.35.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.34.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.34.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.33.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.32.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.31.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.29.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.28.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.27.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.27.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.8.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-06. 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.