@cline/shared
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 | missing-githead | AI (provenance): CI-driven monorepo publish cadence; no behavioral change vs approved sibling. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Expected for automated multi-package monorepo release cadence. | ai | |
| phantom-deps | phantom-dep:aws4fetch | AI (phantom-deps): Declared runtime dep; used via subpath exports not directly traced by phantom-dep heuristic. | ai | |
| phantom-deps | phantom-dep:jsonrepair | AI (phantom-deps): Declared runtime dep; used via subpath exports not directly traced by phantom-dep heuristic. | ai | |
| phantom-deps | phantom-dep:zod-to-json-schema | AI (phantom-deps): Declared runtime dep; used via subpath exports not directly traced by phantom-dep heuristic. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 0.0.65 | 4 / 0 | |
| 0.0.64 | 4 / 0 | |
| 0.0.63 | 4 / 0 | |
| 0.0.62 | 4 / 0 | |
| 0.0.61 | 4 / 0 | |
| 0.0.60 | 4 / 0 | |
| 0.0.59 | 4 / 0 | |
| 0.0.58 | 4 / 0 | |
| 0.0.57 | 4 / 0 | |
| 0.0.56 | 4 / 0 | |
| 0.0.55 | 4 / 0 | |
| 0.0.54 | 4 / 0 | |
| 0.0.53 | 4 / 0 | |
| 0.0.52 | 4 / 0 | |
| 0.0.51 | 4 / 0 | |
| 0.0.50 | 4 / 0 | |
| 0.0.49 | 4 / 0 | |
| 0.0.48 | 4 / 0 | |
| 0.0.47 | 4 / 0 | |
| 0.0.46 | 4 / 0 | |
| 0.0.45 | 4 / 0 | |
| 0.0.44 | 4 / 0 | |
| 0.0.43 | 4 / 0 | |
| 0.0.42 | 4 / 0 | |
| 0.0.41 | 4 / 0 | |
| 0.0.40 | 4 / 0 | |
| 0.0.39 | 4 / 0 | |
| 0.0.38 | 3 / 0 |
v0.0.65
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.64
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.63
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.62
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.61
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.60
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.59
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.58
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.57
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.56
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.55
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.54
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.