80
/ 100
Well engineered. The main gaps are issue and PR templates and a reproducible setup.
Metal I/O library for Rust.
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 2README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Reproducibility6pt
Run `cargo build` and commit the resulting Cargo.lock file.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
74
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
76
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
No Cargo.lock found (−70 pts). Rust binary/application crates should commit Cargo.lock.
→ Run `cargo build` and commit the resulting Cargo.lock file.
Test files detected (tests).
CI is configured (.github/workflows/ci.yml).
Rust linting configured (cargo clippy in CI, cargo fmt in CI).
Project health
98
Dependency manifest found (Cargo.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 15 / 22Commits (30d / 90d)
- 856Forks
- 3Releaseslatest 4y ago
Community
- 37% - WeakCommunity health
- 2 bus factorauthors own >50% of commits
- 7,069Watchers
Responsiveness
- 11hMedian issue response
- 15hMedian PR merge time
- 21Open issues
Repository files10 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- examples
- src
- testsGood: Test files detected (tests).
- .gitignoreGood: .gitignore present.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CHANGELOG.md
- LICENSEGood: Licensed under MIT.
- Makefile
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.Good: README has code examples.Good: README links to a live demo or deployed app.Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.Good: README documents how to install the project.Good: README documents how to run the project.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/tokio-rs/mio)