@cleocode/agents
CLEO agent protocols and templates
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 7 of 207)
| Version | Deps | Published |
|---|---|---|
| 2026.3.44 | 0 / 0 | |
| 2026.3.43 | 0 / 0 | |
| 2026.3.42 | 0 / 0 | |
| 2026.3.41 | 0 / 0 | |
| 2026.3.40 | 0 / 0 | |
| 2026.3.39 | 0 / 0 | |
| 2026.3.37 | 0 / 0 |
v2026.3.44
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.3.43
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.3.42
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.3.41
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.3.40
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.3.39
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.3.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.