83
/ 100
Popular and well-maintained. A little polish away from elite status.
JSON for Modern C++
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.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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
94
CONTRIBUTING guide found.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
69
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.
CI is configured (.github/workflows/check_amalgamation.yml).
Test files detected (tests).
Lockfile present (docs/mkdocs/requirements.txt). Installs are reproducible.
Issue or PR templates present.
Project health
100
Dependency manifest found (Package.swift).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 31 / 78Commits (30d / 90d)
- 7,423Forks
- 45Releaseslatest 9y ago
Community
- 100% - GoodCommunity health
- -authors own >50% of commits
- 50,095Watchers
Responsiveness
- 23hMedian issue response
- 7hMedian PR merge time
- 69Open issues
Repository files25 root entries
- .githubGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: Code of conduct present.Good: CI is configured (.github/workflows/check_amalgamation.yml).Good: Dependabot covers 6 ecosystems (github-actions, pip, pip, pip, pip, pip). Dependencies stay current.Good: Issue or PR templates present.Good: Security policy present.
- .reuse
- cmake
- docsGood: Lockfile present (docs/mkdocs/requirements.txt). Installs are reproducible.
- include
- LICENSES
- single_include
- src
- testsGood: Test files detected (tests).
- tools
- .cirrus.yml
- .clang-tidy
- .gitignoreGood: .gitignore present.
- BUILD.bazel
- ChangeLog.md
- CITATION.cff
- CMakeLists.txt
- FILES.md
- LICENSE.MITGood: Licensed under MIT.
- Makefile
- meson.build
- MODULE.bazel
- nlohmann_json.natvis
- Package.swiftGood: Dependency manifest found (Package.swift).
- 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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/nlohmann/json)