@memberjunction/auth-providers
Authentication provider interfaces, base classes, and implementations for MemberJunction
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 publisher with SLSA attestation is a legitimate supply chain improvement, not a compromise. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Added deps (graphql, jwks-rsa, jsonwebtoken, @memberjunction/core/global) are established packages appropriate for an auth-providers library. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New source files consistent with expanded auth-provider implementations; SLSA provenance covers the build integrity. | ai | |
| dependencies | unvetted-dep:@memberjunction/core | AI (dependencies): Internal monorepo sibling dependency; unvetted status reflects review lag, not a supply-chain concern. | ai | |
| dependencies | unvetted-dep:@memberjunction/global | AI (dependencies): Internal monorepo sibling dependency; same reasoning as @memberjunction/core. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 5.39.0 | 5 / 5 | |
| 5.38.0 | 5 / 5 | |
| 5.37.0 | 5 / 5 | |
| 5.36.0 | 5 / 5 | |
| 5.35.0 | 5 / 5 | |
| 5.34.1 | 5 / 5 | |
| 5.34.0 | 5 / 5 | |
| 5.33.0 | 5 / 5 | |
| 5.32.0 | 5 / 5 | |
| 5.31.0 | 5 / 5 | |
| 5.30.1 | 5 / 5 | |
| 5.30.0 | 5 / 5 | |
| 5.29.0 | 5 / 5 | |
| 5.28.0 | 5 / 5 | |
| 5.27.1 | 5 / 5 | |
| 5.27.0 | 5 / 5 | |
| 5.26.0 | 5 / 5 | |
| 5.25.0 | 5 / 5 | |
| 5.24.0 | 5 / 5 | |
| 5.23.0 | 5 / 5 | |
| 5.22.0 | 5 / 5 | |
| 5.21.0 | 5 / 5 | |
| 5.20.0 | 5 / 5 | |
| 5.19.0 | 5 / 5 | |
| 5.18.0 | 5 / 5 | |
| 5.17.0 | 5 / 5 | |
| 5.16.0 | 5 / 5 | |
| 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.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.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
2 findingsThis version was published by a different npm account than previous versions on 2026-03-24. 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.16.0
1 findingPublished 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.