simdjson/simdjson
Grade a repo

81

/ 100

GradeB

Well engineered. The main gaps are CI and setup instructions.

Top 30% of 5,156 graded repos

Parsing gigabytes of JSON per second : used by Facebook/Meta Velox, the Node.js runtime, ClickHouse, WatermelonDB, Apache Doris, Milvus, StarRocks

Documentation75
Engineering78
Health100
C++23,947Apache-2.029d ago

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

75

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

Contributing guide5pt75

Contributing guide is detailed and thorough.

README12pt85

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

78

CI/CD14pt57

CI is configured (.github/workflows/cifuzz.yml).

Tests18pt80

Test files detected (tests).

Reproducibility6pt80

Lockfile present (benchmark/static_reflect/serde-benchmark/Cargo.lock). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (benchmark/static_reflect/serde-benchmark/Cargo.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 6 / 52
    Commits (30d / 90d)
  • 1,263
    Forks
  • 110
    Releaseslatest 6y ago

Community

  • 75% - Good
    Community health
  • -
    authors own >50% of commits
  • 23,947
    Watchers

Responsiveness

  • 1d 12h
    Median issue response
  • 9h
    Median PR merge time
  • 131
    Open issues
Repository files42 root entries
  • .github
    Good: CI is configured (.github/workflows/cifuzz.yml).
    Good: Issue or PR templates present.
  • .vscode
  • benchmark
    Good: Lockfile present (benchmark/static_reflect/serde-benchmark/Cargo.lock). Installs are reproducible.
    Good: Dependency manifest found (benchmark/static_reflect/serde-benchmark/Cargo.toml).
  • cmake
  • dependencies
  • doc
  • examples
  • extra
  • fuzz
  • images
  • include
  • jsonexamples
  • p2996
    Good: Environment pinned via p2996/Dockerfile.
  • scripts
  • singleheader
  • src
  • style
  • tests
    Good: Test files detected (tests).
  • tools
  • windows
  • .appveyor.yml
  • .cirrus.yml
  • .clang-format
  • .clangd
  • .dockerignore
  • .drone.yml
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .travis.yml
  • AI_USAGE_POLICY.md
  • AUTHORS
  • CMakeLists.txt
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Good: Contributing guide describes code style expectations.
    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.
  • CONTRIBUTORS
  • Doxyfile
  • HACKING.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • LICENSE-MIT
  • README.md
    Good: README is present.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
    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.
    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.md
    Good: Security policy present.
  • simdjson.pc.in
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/simdjson/simdjson)](https://www.repo-grade.com/report/simdjson/simdjson)

More graded C++ repos