rust-lang/api-guidelines resource
Rust API guidelines observed · 2026-08-28
Health v2 · maintenance only
46/100
- Activity 30
- Release rhythm 35
- Longevity 100
Flags: no_releases
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3495
- days_rel: n/a
- days_push: 421
- n_releases_24m: 0
Adoption not part of the score
1346 stars · 121 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
The official Rust API guidelines, a set of recommendations from the Rust library team on designing and presenting idiomatic Rust APIs. It is published as a book with a concise checklist plus detailed topical chapters.
Use cases
- design idiomatic rust crate apis
- review a rust library for api consistency
- learn rust api naming conventions
- checklist for publishing a rust crate
- make my rust library interoperate well with the ecosystem
When to choose
- you are authoring or reviewing a Rust crate and want idiomatic, interoperable API design guidance
- you want an authoritative checklist maintained by the Rust library team
When to avoid
- you need executable lint rules rather than prose guidelines (use clippy instead)
- you are designing APIs in languages other than Rust
Facets
learning-resource · maturity active
documentation programming-languages developer-tools documentation rust api-design guidelines rust-library-team best-practices idiomatic-rust
2 sources
- readme: https://github.com/rust-lang/api-guidelines · fetched 2026-08-28 · fb1567bed8c1
- homepage: https://rust-lang.github.io/api-guidelines/ · fetched 2026-08-29 · b941b302fb04
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| rust-lang/api-guidelines | main | 46 |
For agents
markdown · JSON · MCP: product_card(name="rust-lang/api-guidelines")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem