92
/ 100
A well-known project done right. Strong docs and solid engineering throughout.
Application level tracing 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
If this crate also ships a binary, commit Cargo.lock. For pure library crates, omitting it is recommended per the Cargo guide.
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
83
README is present.
Contributing guide is detailed and thorough.
README documents how to install the project.
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 (tracing-attributes/tests).
CI is configured (.github/workflows/CI.yml).
Rust linting configured (cargo fmt in CI).
Issue or PR templates present.
Project health
100
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
- 0 / 6Commits (30d / 90d)
- 902Forks
- 110Releaseslatest 4y ago
Community
- 87% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 6,756Watchers
Responsiveness
- 14hMedian issue response
- 2hMedian PR merge time
- 856Open issues
Repository files29 root entries
- .cargo
- .config
- .githubGood: CI is configured (.github/workflows/CI.yml).Good: Issue or PR templates present.
- assets
- bin
- examples
- tracing
- tracing-appender
- tracing-attributesGood: Test files detected (tracing-attributes/tests).
- tracing-core
- tracing-error
- tracing-flame
- tracing-futures
- tracing-journald
- tracing-log
- tracing-macros
- tracing-mock
- tracing-serde
- tracing-subscriber
- tracing-test
- tracing-tower
- .gitignoreGood: .gitignore present.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- clippy.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.
- netlify.toml
- 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.
- SECURITY.mdGood: Security policy present.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/tokio-rs/tracing)