@peac/cli
PEAC protocol command-line tools
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @peac/cli is a scoped CLI for the PEAC Protocol project; Levenshtein match to 'joi' is coincidental. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): chalk is declared in dependencies and used by the CLI; phantom-dep heuristic misfires here. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 9 / 4 | |
| 0.14.5 | 9 / 4 | |
| 0.14.4 | 9 / 4 | |
| 0.14.3 | 9 / 4 | |
| 0.14.2 | 9 / 4 | |
| 0.14.1 | 9 / 4 | |
| 0.14.0 | 9 / 4 | |
| 0.13.4 | 9 / 4 | |
| 0.13.3 | 9 / 4 | |
| 0.13.2 | 9 / 4 | |
| 0.13.1 | 9 / 4 | |
| 0.13.0 | 8 / 4 | |
| 0.12.14 | 8 / 4 | |
| 0.12.13 | 8 / 4 | |
| 0.12.12 | 8 / 4 | |
| 0.12.11 | 8 / 4 | |
| 0.12.10 | 8 / 4 | |
| 0.12.9 | 8 / 4 | |
| 0.12.8 | 8 / 4 | |
| 0.12.7 | 8 / 4 | |
| 0.12.6 | 8 / 4 | |
| 0.12.5 | 8 / 4 | |
| 0.12.4 | 8 / 4 | |
| 0.12.3 | 8 / 4 | |
| 0.12.2 | 8 / 4 | |
| 0.12.1 | 8 / 4 | |
| 0.12.0 | 8 / 4 | |
| 0.11.3 | 8 / 4 | |
| 0.11.2 | 8 / 4 | |
| 0.9.18 | 7 / 3 |
v0.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.