@clef-sh/cli
CLI for Clef — git-native secrets management
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 from manual publish to GitHub Actions CI with SLSA provenance; expected and documented by attestation. | ai | |
| phantom-deps | phantom-dep:@clef-sh/ui | AI (phantom-deps): Same-org dep declared but not directly imported; consistent with monorepo peer-dep pattern. | ai | |
| phantom-deps | phantom-dep:@clef-sh/cloud | AI (phantom-deps): Same-org dep declared but not directly imported; consistent with monorepo peer-dep pattern. | ai | |
| phantom-deps | phantom-dep:@clef-sh/analytics | AI (phantom-deps): Same-org dep declared but not directly imported; consistent with monorepo peer-dep pattern. | ai | |
| dependencies | unvetted-dep:@clef-sh/agent | AI (dependencies): Same-org monorepo dependency; consistent pattern across all @clef-sh/* packages. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @clef-sh/cli is a scoped secrets-management CLI; Levenshtein match to 'joi' is a false positive. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.1.28 | 8 / 12 | |
| 0.1.27 | 8 / 12 | |
| 0.1.26 | 8 / 12 | |
| 0.1.25 | 8 / 12 | |
| 0.1.24 | 8 / 12 | |
| 0.1.23 | 3 / 18 | |
| 0.1.22 | 3 / 18 | |
| 0.1.21 | 3 / 16 | |
| 0.1.20 | 3 / 16 | |
| 0.1.19 | 3 / 16 | |
| 0.1.18 | 3 / 16 | |
| 0.1.17 | 3 / 14 | |
| 0.1.16 | 3 / 14 | |
| 0.1.15 | 3 / 14 | |
| 0.1.14 | 3 / 14 | |
| 0.1.13 | 3 / 14 | |
| 0.1.12 | 3 / 14 | |
| 0.1.10 | 0 / 12 |
v0.1.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.14
2 findingsThis version was published by a different npm account than previous versions on 2026-04-10. 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.1.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.