@memberjunction/archiving-engine
Core archiving engine for MemberJunction - handles field-level archiving, storage, and recovery of entity records.
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 individual account to GitHub Actions CI/CD is a standard monorepo automation pattern, backed by SLSA attestation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are same-version @memberjunction/* siblings from the same monorepo release; not third-party additions. | ai | |
| dependencies | unvetted-dep:@memberjunction/core | AI (dependencies): Sibling monorepo package pinned to same version; consistent with coordinated release. | ai | |
| dependencies | unvetted-dep:@memberjunction/global | AI (dependencies): Sibling monorepo package pinned to same version; consistent with coordinated release. | ai | |
| dependencies | unvetted-dep:@memberjunction/storage | AI (dependencies): Sibling monorepo package pinned to same version; consistent with coordinated release. | ai | |
| dependencies | unvetted-dep:@memberjunction/core-entities | AI (dependencies): Sibling monorepo package pinned to same version; consistent with coordinated release. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 5.39.0 | 4 / 2 | |
| 5.38.0 | 4 / 2 | |
| 5.37.0 | 4 / 2 | |
| 5.36.0 | 4 / 2 | |
| 5.35.0 | 4 / 2 | |
| 5.34.1 | 4 / 2 | |
| 5.34.0 | 4 / 2 | |
| 5.33.0 | 4 / 2 | |
| 5.32.0 | 4 / 2 | |
| 5.31.0 | 4 / 2 | |
| 5.30.1 | 4 / 2 | |
| 5.30.0 | 4 / 2 | |
| 5.29.0 | 4 / 2 | |
| 0.0.1 | 0 / 0 |
v5.39.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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
2 findingsThis version was published by a different npm account than previous versions on 2026-04-27. 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.29.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-22. 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.