85
/ 100
A well-known project done right. Strong docs and solid engineering throughout.
Strongly typed JSON library for Rust
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 2Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 3Reproducibility6pt
Run `cargo build` and commit the resulting Cargo.lock file.
- 4Reproducibility6pt
Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
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
89
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.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
76
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.
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).
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)
- 651Forks
- 180Releaseslatest 9y ago
Community
- 50% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 5,596Watchers
Responsiveness
- 36d 19hMedian issue response
- 10d 17hMedian PR merge time
- 226Open issues
Repository files11 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- fuzz
- src
- testsGood: Test files detected (tests).
- .gitignoreGood: .gitignore present.
- build.rs
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- 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.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- LICENSE-APACHE
- LICENSE-MIT
- 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.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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/serde-rs/json)