86
/ 100
Well engineered. The main gaps are a reproducible setup and setup instructions.
An HTTP library for Rust
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
- 2Install and run instructions9pt
Add a section showing how to install dependencies.
- 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
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README is present.
Licensed under MIT.
Engineering
88
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).
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
- 14 / 47Commits (30d / 90d)
- 1,768Forks
- 190Releaseslatest 11y ago
Community
- 87% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 16,213Watchers
Responsiveness
- 8hMedian issue response
- 9hMedian PR merge time
- 260Open issues
Repository files14 root entries
- .githubGood: CI is configured (.github/workflows/CI.yml).Good: Issue or PR templates present.
- benches
- capi
- docsGood: Code of conduct present.
- examples
- src
- testsGood: Test files detected (tests).
- .gitignoreGood: .gitignore present.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CHANGELOG.md
- CONTRIBUTING.mdIssue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.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.Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Good: Contributing guide describes the PR/review workflow.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- LICENSEGood: Licensed under MIT.
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.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.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/hyperium/hyper)