i6eal.de
DEEN
Start a project
← Back to the AI Code RadarSource-backed technology dossier

LiteLLM

oci:ghcr.io/berriai/litellm
model-api

This dossier groups exact published references to one stable package or container identity. Counts are evidence—not market share or deployment.

A technology identity is counted only when the allowlisted parser finds its exact package or container reference. Similar names and descriptive claims remain excluded.

exact identity + commit SHA + exact file path
1repositories
3evidence rows
3with exact version
containerEcosystem
Exact published evidence

Repositories and files carrying this identity

Every row keeps the exact source path and commit SHA. Open the source to inspect the evidence in its original context.

container_reference · direct declarationkiva-llm-gatewaydeploy/Dockerfile.ghcr_base
Exact identityLiteLLMoci:ghcr.io/berriai/litellm
Versionmain-latest4a5cd798be
Open exact source ↗
container_reference · direct declarationkiva-llm-gatewaydocker-compose.yml
Exact identityLiteLLMoci:ghcr.io/berriai/litellm
Versionmain-stable4a5cd798be
Open exact source ↗
container_reference · direct declarationkiva-llm-gatewaydocker/Dockerfile.custom_ui
Exact identityLiteLLMoci:ghcr.io/berriai/litellm
Versionlitellm_fwd_server_root_path-dev4a5cd798be
Open exact source ↗
Stable profile

Machine-readable identity and observation window

Exact identity
oci:ghcr.io/berriai/litellm
Category
model-api
Ecosystem
container
First observed
18 Jul 2026
Last observed
18 Jul 2026
Interpretation boundary

What this page can—and cannot—show

The page is a deterministic projection of official public GitLab data. A missing row means not observed within the bounded files and checkpoint, not absent in reality.

Retrieval, parsing and publishing use no generative AI model.Open official source ↗

i6eal (2026): LiteLLM — source-backed AI code evidence dossier, data state 18 Jul 2026. https://i6eal.de/en/tools/ki-code-radar/technologie/ghcr-io-berriai-litellm-cfece842/

Reading this dossier

Does this dossier prove productive use?
No. It documents only an exact technology reference published in code at an observed commit.
Why are the commit SHA and file path retained?
Together with the stable GitLab project ID, they make every displayed finding inspectable and resistant to later repository changes.
What does a missing version mean?
The exact identity was observable, but the inspected source did not publish a version that the deterministic parser could retain.

Need a permanent evidence trail for another public dataset?

Discuss a data projectExplore all tools
Related tools

Useful next steps

These tools complement the current result.

View all tools
MonitorGerman public-sector AI registerWhere does German public administration already use AI? Search published system profiles from federal, state and municipal bodies, with lifecycle, governance fields, stable identifiers and original evidence.IndexAI Procurement & Supplier IndexWhich AI contracts does the public sector award, who wins, and which technology dependencies are explicitly disclosed? Procurement updates daily from TED and oeffentlichevergabe.de; suppliers use exact source IDs only.MonitorPublic AI signal chronicleSee what actually changed across public AI data: new projects, updated evidence and corrections in an append-only chronicle with observation time, source identifier and direct link.