63
/ 100
Popular for its size, but the engineering basics lag behind the interest.
A collection of RBIR projects and posts for anyone interested in joining this journey.
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 B (80).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add integration tests in a tests/ directory or unit tests via #[cfg(test)] blocks.
- 2README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 3README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
- 4Install and run instructions9pt
Add a section showing how to install dependencies.
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
37
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Engineering
68
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.
Cargo.toml has dev-dependencies (may include test tooling).
Lockfile present (Cargo.lock). Installs are reproducible.
CI is configured (.github/workflows/ci.yml).
Rust linting configured (rustfmt.toml, cargo clippy in CI, cargo fmt in CI).
Project health
94
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)
- 13Forks
- 0Releases
Community
- 37% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 325Watchers
Responsiveness
- 3hMedian issue response
- <1hMedian PR merge time
- 10Open issues
Repository files13 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- libraries
- projects
- src
- templates
- .gitignoreGood: .gitignore present.
- .taplo.toml
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- data.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.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.
- rust-toolchain.toml
- rustfmt.tomlGood: Rust linting configured (rustfmt.toml, cargo clippy in CI, cargo fmt in CI).
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/rewrite-bigdata-in-rust/rbir)