Report · marked 25 Aug 2026
apache/airflow
Solid foundations, held back in a few specific places.
Python · 46,606 stars · 13,892 files · branch main
80
/100
A-
Instructions
25/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality.Setup
14/20Whether an agent can install the project and get it running without a human. Losing marks on environment config and pinned runtime version.Verification loop
24/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on static type checking.Context economy
9/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
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
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.
03
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.
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.
Also found: CLAUDE.md
✗Instruction quality
10/12
Specific enough that an agent can act on it.
Worth fixing: it's 36k characters, which burns context on every single turn.
names the actual commands to run
uses headings, so an agent can skim it
includes copyable code blocks
✓README as an entry point
3/3
README has a clear getting-started section.
Setup 14/20 B+
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.
pyproject.toml scripts
✗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
0/2
No pinned runtime version.
Add a .nvmrc, .python-version, or equivalent so the agent's toolchain matches yours.
✓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
4434 test files against 8986 source files.
e.g. airflow-core/src/airflow/api_fastapi/auth/managers/simple/ui/src/login/Login.test.tsx, airflow-core/src/airflow/api_fastapi/execution_api/datamodels/connection_test.py, airflow-core/src/airflow/executors/workloads/connection_test.py
✓Test command is discoverable
7/7
An agent can find and run `pytest`.
✓Continuous integration
4/4
52 GitHub Actions workflows define what "passing" means.
✓Lint and format rules
3/3
pyproject.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 188 patterns.
✗File sizes fit in context
0/6
52 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.
airflow-core/tests/unit/jobs/test_scheduler_job.py — 568KB
airflow-core/tests/unit/api_fastapi/core_api/routes/public/test_task_instances.py — 306KB
airflow-core/src/airflow/ui/openapi-gen/requests/schemas.gen.ts — 291KB
✗Repository weight
0/5
About 698MB 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 Apache Airflow - A platform to programmatically author, schedule, and monitor workflows ## Setup ``` uv sync ``` ## Commands ``` pytest # run the test suite ruff check . # lint ``` ## Layout - `providers/` 5474 source files - `airflow-core/` 2072 source files - `scripts/` 320 source files - `task-sdk/` 254 source files - `dev/` 235 source files - `devel-common/` 105 source files ## Conventions - Tests live alongside the code they cover, following `airflow-core/src/airflow/api_fastapi/auth/managers/simple/ui/src/login/Login.test.tsx`. - CI defines what passing means. See `.github/workflows/additional-ci-image-checks.yml`, and keep it green. - TODO: add the two or three conventions a newcomer always gets wrong here. ## Gotchas - `airflow-core/tests/unit/jobs/test_scheduler_job.py` is 568KB. 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/apache/airflow.md
Show the mark
The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.
[](https://agentreadme.com/apache/airflow)Other Python repositories, marked
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.