0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
Easy E2E testing for Axum
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to A (90).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
- 2Install and run instructions9pt
Add a section showing how to install dependencies.
- 3Install and run instructions9pt
Add a section showing how to start or use the project.
- 4Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
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
56
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
Licensed under MIT.
Engineering
49
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
No Rust linting or formatting enforced.
→ Add `cargo clippy -- -D warnings` and `cargo fmt --check` as CI steps, and optionally a rustfmt.toml for project-specific style rules.
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).
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
- -Commits (30d / 90d)
- 29Forks
- 2Releaseslatest 5mo ago
Community
- -Community health
- -authors own >50% of commits
- 262Watchers
Responsiveness
- 11hMedian issue response
- <1hMedian PR merge time
- 4Open issues
Repository files12 root entries
- .githubGood: Issue or PR templates present.
- examples
- files
- src
- testsGood: Test files detected (tests).
- .gitignoreGood: .gitignore present.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CLAUDE.md
- LICENSEGood: Licensed under MIT.
- makefile
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Good: README has code examples.Good: README links to a live demo or deployed app.Good: README includes status badges.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.
- rust-toolchain
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/josephlenton/axum-test)