@memberjunction/lists
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 5.40.2 | 4 / 3 | |
| 5.40.1 | 4 / 3 | |
| 5.40.0 | 4 / 3 | |
| 5.39.0 | 4 / 3 | |
| 5.38.0 | 4 / 3 | |
| 5.37.0 | 4 / 3 | |
| 5.36.0 | 4 / 3 | |
| 0.0.1 | 0 / 0 |
v5.40.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.40.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.40.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.