Repo brief: tokio-rs/axum

Generated by RepoPilot · document generated 2026-09-15 · concise human review Evidence snapshot · analyzed 2026-09-15T03:51:02.469Z · commit 3d78036dcac2

Verdict

Healthy — Healthy across all four use cases

• Last commit 1d ago
• 42+ active contributors
• Distributed ownership (top contributor 16% of recent commits)
• MIT licensed
• 2 more receipts on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

What it is

Axum is a modular, ergonomic HTTP routing and request-handling library for Rust that prioritizes composability and developer experience. It provides typed request extractors, response builders, and middleware patterns for building production web services with minimal boilerplate, built on top of Tokio async runtime. Monorepo with three main crates: axum (core routing), axum-core (foundational extractors and responses), and axum-extra (optional features like cookies, multipart, JSON deserialization). Each crate has its own Cargo.toml, CHANGELOG, and LICENSE. Core abstractions live in axum-core/src/extract/ (typed request extractors) and axum-core/src/response/ (response builders).

Start here

Open these first:

• axum/src/extract/mod.rs — Core extraction trait and implementation that defines how HTTP requests are deserialized into handler arguments.
• axum-core/src/response/into_response.rs — Central response conversion mechanism that transforms handler return values into HTTP responses.
• axum/Cargo.toml — Main crate dependencies and feature flags that define axum's modular architecture across core, extra, and macros.
• axum-core/src/lib.rs — Core library entry point exposing fundamental traits and types used across all axum crates.
• axum-macros/src/lib.rs — Procedural macros library providing compile-time code generation for handlers, extractors, and typed paths.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

1. Clone: git clone https://github.com/tokio-rs/axum.git && cd axum
2. Build: cargo build (workspace resolver 2 is configured)
3. Run tests: cargo test --all (tests likely in each crate)
4. Check examples: Look for examples/ directories if present (not shown in file list).

Daily commands:

No Makefile or package.json present. For a library, there is no 'dev server.' To develop: (1) cargo build to compile, (2) cargo test to run tests, (3) cargo doc --open to view docs, (4) Look for examples/ director…

…shortened for this brief.

Key cautions & unknowns

• No obvious global secrets or environment variables in the provided data. Trap: crate dependencies—axum-extra depends on axum and axum-core; axum likely depends on axum-core. Verify via Cargo.toml files to avoid…
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.