tokio-rs/axum
GitHubHTTP routing and request-handling library for Rust that focuses on ergonomics and modularity
- Stars:
- 27.7k
- Language:
- Rust
- Default branch:
- main
- Last scored:
At a glance
- Rank
- #329 of 401
- #40 of 45 Rust repos
- Checks passed
- 7 of 17
- Full list below
- Best set up for
- Codex
- Score 59.0
- Needs most work for
- Aider
- Biggest fix: .aider.conf.yml (+14.1 pts)
What it has
What it's missing
What to fix first
Showing fixes for Claude Code
- 1AGENTS.md / CLAUDE.mdAdd an AGENTS.md covering project goals, layout, setup commands, and conventions. Aim for 800+ chars of real guidance (not boilerplate).+13.2 pts
- 2Reproducible dev envAdd a Makefile or devcontainer or Dockerfile so the agent can set up the project in one command.+11.8 pts
- 3Linter / formatter configConfigure a linter/formatter (ESLint+Prettier, Biome, Ruff, rustfmt+clippy, golangci-lint) and commit the config.+7.9 pts
Score for each AI agent
Each agent weighs the checks by its own docs. Under each score are its top three. How each agent is scored →
Does tokio-rs/axum have agent instructions?
An AGENTS.md (or CLAUDE.md) at the root tells AI coding agents how to build, test and work in the repo. A few agents also read a file of their own.
- AGENTS.md / CLAUDE.md
- None at the root (no AGENTS.md, CLAUDE.md, AGENT.md, .claude/CLAUDE.md or .claude/AGENTS.md)
- Agent-specific files
- None: no GEMINI.md, .cursor/rules, .openhands/setup.sh, .aider.conf.yml or .agents/skills
- Repos that have one
- 24 of 45 Rust repos · 222 of 401 repos on the leaderboard · See examples →
Get a starter AGENTS.md
From the files the checks found. Fill in the commands, then commit it at the root.
# AGENTS.md
Guidance for AI coding agents working in tokio-rs/axum. HTTP routing and request-handling library for Rust that focuses on ergonomics and modularity. Written mainly in Rust.
## Where things are
- Dependencies are declared in `Cargo.toml`.
- Test files are spread through the tree, e.g. `axum-macros/src/axum_test.rs`.
- CI is defined in `.github/workflows`; read it for the exact install, lint and test steps.
- Follow the conventions in `CONTRIBUTING.md`.
## Commands
<!-- Fill in the exact commands CI runs. -->
- Install: TODO
- Test: TODO
- Lint: TODO
All 17 checks · 7 passed
How tokio-rs/axum compares
- vs leaderboard average
- 11.3 pts below
- Average 66.9
- vs Rust average
- 15.0 pts below
- Average 70.6
- Stars among Rust repos
- #32 of 45
Missing here, and how many repos have it
- Linter / formatter config · passed by 65% of leaderboard repos, 80% of Rust repos
- Pre-commit / git hooks · passed by 29% of leaderboard repos, 20% of Rust repos
- Reproducible dev env · passed by 22% of leaderboard repos, 33% of Rust repos
Passes checks most repos miss
- Manageable size · only 16% of repos pass it
One fix for the most agents: Linter / formatter config would raise the score for all 9 agents, by up to 14.1 points.
Similar repos
Same language and host as this repo, closest in overall score.
- openai/codex60.2Rust · 133.3k ★
- Rust · 66.1k ★
- tokio-rs/tokio54.4Rust · 33.6k ★
- gleam-lang/gleam54.0Rust · 22k ★
- rayon-rs/rayon50.4Rust · 13.4k ★
- Rust · 11.9k ★
Same topics, any language
Repos tagged with the same GitHub topics, most shared first.
- TanStack/router78.6TypeScript · routing
- aio-libs/aiohttp88.1Python · HTTP
- vapor/vapor81.8Swift · HTTP
- psf/requests81.3Python · HTTP
- Go · HTTP
- Kludex/starlette72.1Python · HTTP
Add a badge to your README
Paste this at the top of the README. It shows the score, and links back to this page.
[](https://agentfriendlycode.com/repo/github/tokio-rs/axum)Check the score on every pull request
A GitHub Action posts one comment per pull request with how the score changed and why.