Read 2026-10-04
tokio-rs/axum: technical due diligence, read from its repository
What Borehole read in tokio-rs/axum's code and history at bc8d491: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | strong |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongaxum/src/serve/mod.rs is 2,010 lines, 33× this codebase's median file
adequateThe median source file here is 60 lines. 6 files exceed 1,000 lines, the largest being 2,010. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
axum/src/serve/mod.rs:1 — 2,010 lines (33× median) |
axum/src/routing/method_routing.rs:1 — 1,771 lines (29× median) |
axum/src/extract/ws.rs:1 — 1,317 lines (21× median) |
axum/src/extract/path/mod.rs:1 — 1,087 lines (18× median) |
axum-macros/src/from_request/mod.rs:1 — 1,076 lines (17× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate11% of bug fixes add or change a test
adequateOf 89 fixes in the last 24 months, 10 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 10 of 89 |
Security & Reliability Posture
adequate1 credential-shaped string in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| JWT, where fakes are usual |
The build runs third-party code it does not pin
adequate6 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
.github/workflows/CI.yml:22 — action pinned by tag |
.github/workflows/CI.yml:25 — action pinned by tag |
2 locked dependencies have published vulnerabilities
adequate2 of 238 locked dependencies match 2 published advisories in OSV. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
Cargo.lock — rand 0.8.5: GHSA-cq8v-f236-94qc (low), fixed in 0.8.6 |
Cargo.lock — rand 0.9.2: GHSA-cq8v-f236-94qc (low), fixed in 0.9.3 |
Observability & Operations
not assessableNot rated: only 4 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on tokio-rs/axum: every dimension, the questions for the room, and the audit log.
Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.