@memberjunction/archiving-action
Archive and restore actions for MemberJunction Archiving Engine
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): Publisher is GitHub Actions with SLSA attestation; MJ monorepo uses CI/CD publishing, stable pattern. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are @memberjunction/* at the same pinned version — monorepo internal deps, not third-party additions. | ai | |
| dependencies | unvetted-dep:@memberjunction/actions | AI (dependencies): Internal monorepo dependency published at matching version; consistent release pattern. | ai | |
| dependencies | unvetted-dep:@memberjunction/core | AI (dependencies): Internal monorepo dependency published at matching version; consistent release pattern. | ai | |
| dependencies | unvetted-dep:@memberjunction/archiving-engine | AI (dependencies): Internal monorepo dependency published at matching version; consistent release pattern. | ai | |
| dependencies | unvetted-dep:@memberjunction/actions-base | AI (dependencies): Internal monorepo dependency published at matching version; consistent release pattern. | ai | |
| dependencies | unvetted-dep:@memberjunction/global | AI (dependencies): Internal monorepo dependency published at matching version; consistent release pattern. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 5.39.0 | 5 / 0 | |
| 5.38.0 | 5 / 0 | |
| 5.37.0 | 5 / 0 | |
| 5.36.0 | 5 / 0 | |
| 5.35.0 | 5 / 0 | |
| 5.34.1 | 5 / 0 | |
| 5.34.0 | 5 / 0 | |
| 5.33.0 | 5 / 0 | |
| 5.32.0 | 5 / 0 | |
| 5.31.0 | 5 / 0 | |
| 5.30.1 | 5 / 0 | |
| 5.30.0 | 5 / 0 | |
| 5.29.0 | 5 / 0 | |
| 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.