This package has dated incident reports relevant to its trust history. Check the affected releases and the response before drawing conclusions about its current version.
Read the incident coverage →Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.
Review remediation options →Loading historical repository activity…
Signals · last 33 checks
Dated reporting about this package. These events are separate from its current maintenance score.
· PyPI
JFrog documented backdoored PyPI releases after a compromised Trivy build tool exposed publishing credentials. The report describes credential theft and the project’s change to a pinned Trivy version.
Affected versions: 1.82.7 and 1.82.8
Packages: litellm
Source: JFrog Security Research
Third-party facts checked today; registry facts on every crawl.
| When | Change |
|---|---|
| 2026-11-06 | first verdict: active |
account hijacked 2026-03 1.82.7, 1.82.8
Credentials stolen in the same campaign as the Trivy compromise published two releases that harvested environment variables, SSH, cloud and Kubernetes credentials on import and installed persistence.
PyPI quarantined the project; the maintainers told users to treat it as full credential exposure.
Source: Datadog Security Labs analysis, 24 March 2026. History, not a warning about today — the verdict above is about maintenance now.
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/pypi/litellm)Watch it
Get told when litellm changes state, changes licence, or is deprecated — instead of finding out during an incident.
Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.