Report · marked 26 Aug 2026

astral-sh/uv

Solid foundations, held back in a few specific places.

Rust · 89,083 stars · 1,710 files · branch main

83 /100 A-

Instructions 23/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality.Setup 16/20Whether an agent can install the project and get it running without a human. Losing marks on environment config.Verification loop 22/22Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Full marks.Context economy 11/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context and repository weight.Navigability 10/10How quickly anything new can orient itself. Full marks.

Higher is better. Accent marks what is costing you most.

Fix these first

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.

Environment config

Add a .env.example listing every variable with a safe placeholder value. It's the cheapest possible fix and it unblocks the whole first run.

Instruction quality

Worth fixing: has no headings to structure it; has no code blocks.

The full marking

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

Instructions 23/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.

Also found: CLAUDE.md

✗Instruction quality 8/12

Real instructions, with gaps.

Worth fixing: has no headings to structure it; has no code blocks.

1,815 characters, a workable length

names the actual commands to run

✓README as an entry point 3/3

README has a clear getting-started section.

Setup 16/20 A-

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

✓Deterministic install 6/6

uv.lock pins the dependency tree.

Found uv.lock

✓Discoverable commands 6/6

Commands are declared where an agent will look for them.

scripts/ directory

✗Environment config 0/4

Nothing documents the environment this needs. An agent will get a runtime error it can't diagnose.

Add a .env.example listing every variable with a safe placeholder value. It's the cheapest possible fix and it unblocks the whole first run.

✓Pinned runtime version 2/2

The language runtime version is pinned.

Found rust-toolchain.toml

✓Reproducible environment 2/2

dockerfile gives a known-good environment.

Verification loop 22/22 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

598 test files against 753 source files.

e.g. agents/prompts/create-bug-test.md, agents/schemas/create-bug-test.json, crates/uv-cache/tests/removal.rs

✓Test command is discoverable 7/7

An agent can find and run `cargo test`.

✓Continuous integration 4/4

41 GitHub Actions workflows define what "passing" means.

✓Lint and format rules 3/3

ruff.toml encodes the house style.

–Static type checking n/a

Not applicable — the Rust compiler type checks every build.

Context economy 11/20 B-

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 36 patterns.

✗File sizes fit in context 0/6

33 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.

crates/uv/tests/lock/lock.rs — 1705KB

crates/uv/tests/lock_scenarios/lock_conflict.rs — 676KB

crates/uv/tests/pip_compile/pip_compile.rs — 635KB

✗Repository weight 2/5

About 196MB 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 astral-sh/uv

# AGENTS.md

An extremely fast Python package and project manager, written in Rust.

## Setup

```
uv sync
```

## Commands

```
cargo test   # run the test suite
```

## Layout

- `crates/`  644 source files
- `test/`    57 source files
- `scripts/` 42 source files
- `agents/`  6 source files
- `python/`  3 source files
- `docs/`    1 source file

## Conventions

- Tests live alongside the code they cover, following `agents/prompts/create-bug-test.md`.
- CI defines what passing means. See `.github/workflows/bench.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

## Gotchas

- `crates/uv/tests/lock/lock.rs` is 1705KB. It will not fit comfortably in context, so read it in parts.

---

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/astral-sh/uv.md

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](https://agentreadme.com/badge/astral-sh/uv.svg)](https://agentreadme.com/astral-sh/uv)

Other Rust repositories, marked

ultraworkers/claw-code 71 B+ farion1231/cc-switch 63 B rustdesk/rustdesk 70 B+ openai/codex 82 A- rust-lang/rust 65 B tauri-apps/tauri 64 B

All Rust 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