@cleocode/paths
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 8 of 108)
| Version | Deps | Published |
|---|---|---|
| 2026.5.36 | 1 / 3 | |
| 2026.5.35 | 1 / 3 | |
| 2026.5.34 | 1 / 3 | |
| 2026.5.33 | 1 / 3 | |
| 2026.5.29 | 1 / 3 | |
| 2026.5.28 | 1 / 3 | |
| 2026.5.27 | 1 / 3 | |
| 2026.5.26 | 1 / 3 |
v2026.5.36
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.5.35
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.5.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.5.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.5.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.5.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.5.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.5.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.