rust-lang/crates.io

The Rust package registry

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 46 minutes ago
Added to GitGenius on September 18th, 2026
Created on June 30th, 2014
Open Issues & Pull Requests: 110 (+0)
GitHub issues: Enabled
Number of forks: 752
Total Stargazers: 3,700 (+0)
Total Subscribers: 53 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.1 hours
Mean response time: 23.9 days
90th percentile: 30.5 days
Tracked items: 231

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 9% of issues opened in the past year have never received a reply. 58% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "A-infrastructure 📡" is answered fastest, typically in under an hour, while "C-enhancement ✨" waits about 31 hours. 79% of issues opened in the past year have been closed, leaving a working backlog. Three people close 89% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 50
New in 7 days: 1
Closed in 7 days: 3
Avg open age: 935 days
Stale 30+ days: 40
Stale 90+ days: 28

Recent activity

Opened in 7 days: 1
Closed in 7 days: 3
Comments in 7 days: 1
Events in 7 days: 5

Top labels

  • C-bug 🐞 (58)
  • C-enhancement ✨ (49)
  • A-backend ⚙️ (47)
  • A-frontend 🐹 (42)
  • A-infrastructure 📡 (15)
  • A-publish (8)
  • A-accounts (7)
  • C-internal 🔧 (7)

Detailed Description

crates.io is the official package registry for the Rust programming language.

The registry solves the problem of distributing and discovering Rust packages, known as crates, by providing a central hub where developers can publish libraries and other developers can find and depend on them. The service maintains both the website infrastructure and backend systems that handle package storage, metadata management, and discovery.

The tool is essential for anyone working in Rust, as it serves as the primary mechanism for sharing and consuming packages within the ecosystem. It suits projects of any scale that need to leverage community-maintained libraries. The backend is built with Rust using the axum web framework and diesel for database access, along with a custom background worker system. The frontend is a SvelteKit application written in TypeScript. This architecture makes it particularly relevant for developers interested in how a production Rust service is structured and maintained.

The project maintains active engagement with its community through multiple channels including a dedicated Zulip stream, email support, and GitHub Discussions for feature suggestions. The team regularly reviews and addresses bug reports filed in the issue tracker. Contributions are welcomed across bug fixes, new features, and documentation improvements, with structured guidance provided through contribution guidelines and development setup documentation.