agentreadme

Report · marked 9 Oct 2026

BerriAI/litellm

Solid foundations, held back in a few specific places.

Python · 60,436 stars · 14,119 files · branch main

Fix these first

01
File sizes fit in context
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
02
Repository weight
Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.
03
License
Without a license nobody can safely reuse this, and some tools will refuse to work with it at all.

The full marking

Every deduction below names the file or setting it came from.

Instructions 25/27 A+

Whether the repo tells an agent how to behave before it starts guessing.

✓Agent instruction file 12/12
AGENTS.md is present, which is the format the most tools read.
✗Instruction quality 10/12
Specific enough that an agent can act on it.
Worth fixing: has no code blocks.
18,072 characters, a workable length
names the actual commands to run
uses headings, so an agent can skim it
✓README as an entry point 3/3
README has a clear getting-started section.
Setup 20/20 A+

Whether an agent can install the project and get it running without a human.

✓Deterministic install 6/6
package-lock.json pins the dependency tree.
Found package-lock.json
✓Discoverable commands 6/6
Commands are declared where an agent will look for them.
Makefile
pyproject.toml scripts
scripts/ directory
✓Environment config 4/4
.env.example documents what the app needs to run.
✓Pinned runtime version 2/2
The language runtime version is pinned.
Found rust-toolchain.toml
✓Reproducible environment 2/2
.devcontainer/devcontainer.json gives a known-good environment.
Verification loop 24/25 A+

Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.

✓Tests exist 8/8
6459 test files against 11332 source files.
e.g. .github/workflows/helm_unit_test.yml, .github/workflows/mutation-test.yml, cookbook/litellm_router_load_test/test_loadtest_openai_client.py
✓Test command is discoverable 7/7
An agent can find and run `make test`.
✓Continuous integration 4/4
45 GitHub Actions workflows define what "passing" means.
✓Lint and format rules 3/3
ruff.toml encodes the house style.
✗Static type checking 2/3
Type checking is configured, but not in strict mode.
A type checker gives an agent an error message instead of a runtime surprise. It's the second-fastest feedback loop after the compiler.
Context economy 9/20 C

Whether the repo fits in a context window, or fights it.

✓No committed build output 6/6
No generated directories committed.
✓.gitignore hygiene 3/3
.gitignore covers 130 patterns.
✗File sizes fit in context 0/6
161 source files are over 100KB.
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
ui/litellm-dashboard/src/lib/http/schema.d.ts — 2930KB
litellm/proxy/swagger/swagger-ui-bundle.js — 1451KB
tests/unit/test_router/test_router.py — 958KB
✗Repository weight 0/5
About 2064MB checked out. Large enough that cloning and searching are both slow.
Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.

Here is your AGENTS.md

Drafted from what is actually in this repository: the install command from your lockfile, the commands you already declare, your real directory layout. Anything marked TODO needs a person. Save it at the root as AGENTS.md.

AGENTS.md — drafted for BerriAI/litellm
# AGENTS.md

The fastest, litest AI Gateway. Rust core with Python SDK. Call 100+ LLM APIs in OpenAI (or native) format with cost tracking, guardrails, load balancing, and logging [Bedrock, Azure, OpenAI, Anthropic, OpenAI, VertexAI, vLLM, Nvidia NIM]

## Setup

```
npm ci
```

## Commands

```
make help
make info
make install-dev
make bootstrap
make install-proxy-dev
make install-dev-ci
```

## Layout

- `tests/`        4709 source files
- `litellm/`      2763 source files
- `ui/`           2515 source files
- `litellm-rust/` 908 source files
- `enterprise/`   151 source files
- `terraform/`    102 source files

## Conventions

- Tests live alongside the code they cover, following `.github/workflows/helm_unit_test.yml`.
- CI defines what passing means. See `.github/workflows/auto-close-duplicates.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

## Gotchas

- `ui/litellm-dashboard/src/lib/http/schema.d.ts` is 2930KB. It will not fit comfortably in context, so read it in parts.
- Copy `.env.example` before running anything that needs configuration.

---

Drafted by agentreadme.com from what is in this repository. Everything marked TODO
needs a human. Check it in as AGENTS.md at the root.

Open the raw markdown  or  curl -o AGENTS.md agentreadme.com/draft/BerriAI/litellm.md

A draft gets the commands right and stops at the things only a maintainer knows. What a good Python AGENTS.md looks like covers what to add by hand, and what AGENTS.md is explains the format itself.

Show the mark

The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.

agent ready 81 out of 100

[![agent ready](https://agentreadme.com/badge/BerriAI/litellm.svg)](https://agentreadme.com/BerriAI/litellm)

Other Python repositories, marked

vinta/awesome-python 81 A- NousResearch/hermes-agent 84 A- TheAlgorithms/Python 89 A yt-dlp/yt-dlp 54 C+ microsoft/markitdown 48 C+ Significant-Gravitas/AutoGPT 65 B

All Python repositories

Think this mark is wrong?

Every deduction above names the file it came from, so this can be settled by looking. If a check missed something, that is a rule worth fixing.

Open an issue, already filled in