0
/ 100
Solid engineering. The biggest lever is issue and PR templates.
A fast JSON parser/generator for C++ with both SAX/DOM style API
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 3Reproducibility6pt
Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
- 4Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry, or a renovate.json, so dependencies are updated automatically.
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
85
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README documents how to install the project.
README is present.
Licensed under Other.
Engineering
59
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
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 dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
Test files detected (bin/jsonschema/tests).
CI is configured (.travis.yml).
Project health
79
No pushes in over a year (−80 pts).
→ A recent commit signals the project is alive and worth contributing to.
Dependency manifest found (package.json).
Repository has a description.
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 0 / 0Commits (30d / 90d)
- 3,651Forks
- 5Releaseslatest 10y ago
Community
- 37% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 15,121Watchers
Responsiveness
- 3hMedian issue response
- 3hMedian PR merge time
- 795Open issues
Repository files27 root entries
- binGood: Licensed under Other.Good: Test files detected (bin/jsonschema/tests).
- CMakeModules
- contrib
- doc
- dockerGood: Environment pinned via docker/debian/Dockerfile.
- example
- include
- test
- thirdparty
- .gitattributes
- .gitignoreGood: .gitignore present.
- .gitmodules
- .travis.ymlGood: CI is configured (.travis.yml).
- appveyor.yml
- CHANGELOG.md
- CMakeLists.txt
- include_dirs.js
- library.json
- license.txt
- package.jsonGood: Dependency manifest found (package.json).
- rapidjson.autopkg
- RapidJSON.pc.in
- RapidJSONConfig.cmake.in
- RapidJSONConfigVersion.cmake.in
- 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.Good: README documents how to install the project.Good: README documents how to run the project.
- readme.zh-cn.md
- travis-doxygen.sh
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/tencent/rapidjson)