0
/ 100
Solid engineering. The main gap is visibility.
A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
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 section showing how to install dependencies.
- 4Install and run instructions9pt
Add a section showing how to start or use the project.
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
58
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Contributing guide is detailed and thorough.
Licensed under MIT.
Engineering
94
No Cargo.lock committed (correct for Rust library crates; the ecosystem convention is to omit it for libraries).
Test files detected (tests-build/tests).
CI is configured (azure-pipelines.yml).
Rust linting configured (rustfmt.toml).
Issue or PR templates present.
Project health
64
No pushes in over 2 years. Looks unmaintained (−95 pts).
→ A recent commit signals the project is alive and worth using.
Repository has a description.
Dependency manifest found (Cargo.toml).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 0Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 0Open issues
Repository files20 root entries
- .githubGood: Issue or PR templates present.
- bin
- ci
- examples
- tests-buildGood: Test files detected (tests-build/tests).
- tests-integration
- tokio
- tokio-macros
- tokio-test
- tokio-tls
- tokio-util
- .cirrus.yml
- .gitignoreGood: .gitignore present.
- azure-pipelines.ymlGood: CI is configured (azure-pipelines.yml).
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- LICENSEGood: Licensed under MIT.
- 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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- ROADMAP.md
- rustfmt.tomlGood: Rust linting configured (rustfmt.toml).
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/asevans48/tokio)