8 views
-/https://github.com/berriai/litellm/issues/32306
GitHub · issue

#32306 [Bug]: Documented cosign verification fails for LiteLLM Docker image v1.91.0

  • State: open
  • Author: @jeffgyf

# Documented cosign verification fails for LiteLLM Docker image v1.91.0

## Summary

The LiteLLM release notes and README state that Docker images published to GHCR are signed with cosign and can be verified with the public key introduced in commit `0112e53046018d726492c814b3644b7d376029d0`.

However, verification currently fails for `ghcr.io/berriai/litellm:v1.91.0` with `no signatures found`. `cosign tree` also reports no supply-chain security artifacts for the image.

I also checked a local checkout of the repository pipeline files. The `create-release.yml` workflow appears to add cosign verification instructions to the GitHub release body, but I could not find a corresponding `cosign sign` step in the GitHub Actions workflow files, CircleCI config, Docker files, or scripts in that checkout.

Related but distinct issue: #27643 reports release-page cosign links returning 404. This issue reports that the documented verification command resolves the key URL but cannot find image signature artifacts to verify.

## Reproduction

```bash cosign verify \ --key https://raw.githubusercontent.com/BerriAI/litellm/0112e53046018d726492c814b3644b7d376029d0/cosign.pub \ ghcr.io/berriai/lit…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (3 events)
#0 of 0 · 31d19h12m20s ago — entered · #import:https:::github.com:berriai:litellm post #1765
32306 requires secure CI/release-pipeline changes, artifact publication validation, key/signature handling, and end-to-end verification across tooling. 33401 is comparatively localized parameter-gating logic with targeted regression tests.
The right issue is harder because it requires coordinated release-pipeline, registry, signing, verification, and security validation work, with broader deployment risk. The left issue is comparatively localized to request-processing and configuration behavior.
#0 of 0 · 31d18h52m1s ago — current · #import:https:::github.com:berriai:litellm post #2098
Spend-log cleanup requires diagnosing runtime behavior across retention scheduling, batching, persistence, and distributed locking, then adding reliable regression coverage; the signing issue is more narrowly scoped to release-pipeline configuration and verification.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search