0
/ 100
The fundamentals need work — start with test coverage and the README.
C++ Mathematical Expression Parsing And Evaluation Library https://www.partow.net/programming/exprtk/index.html
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 D (69).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add automated tests. They prove the code works and give contributors confidence to make changes.
- 2README12pt
Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
- 3README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 4README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
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
59
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.
README is present.
README documents how to install the project.
Licensed under Other.
Engineering
29
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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 dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
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.
CI is configured (.circleci/config.yml).
Project health
54
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
Actively maintained (pushed within 3 months).
Repository has a description.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 0 / 0Commits (30d / 90d)
- 322Forks
- 0Releases
Community
- 42% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 1,024Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 0Open issues
Repository files33 root entries
- .circleciGood: CI is configured (.circleci/config.yml).
- exprtk_benchmark.cpp
- exprtk_functional_ext_test.txt
- exprtk_functional_test.txt
- exprtk_simple_example_01.cpp
- exprtk_simple_example_02.cpp
- exprtk_simple_example_03.cpp
- exprtk_simple_example_04.cpp
- exprtk_simple_example_05.cpp
- exprtk_simple_example_06.cpp
- exprtk_simple_example_07.cpp
- exprtk_simple_example_08.cpp
- exprtk_simple_example_09.cpp
- exprtk_simple_example_10.cpp
- exprtk_simple_example_11.cpp
- exprtk_simple_example_12.cpp
- exprtk_simple_example_13.cpp
- exprtk_simple_example_14.cpp
- exprtk_simple_example_15.cpp
- exprtk_simple_example_16.cpp
- exprtk_simple_example_17.cpp
- exprtk_simple_example_18.cpp
- exprtk_simple_example_19.cpp
- exprtk_simple_example_20.cpp
- exprtk_simple_example_21.cpp
- exprtk_simple_example_22.cpp
- exprtk_simple_example_23.cpp
- exprtk_simple_example_24.cpp
- exprtk_test.cpp
- exprtk.hpp
- license.txtGood: Licensed under Other.
- Makefile
- readme.txtGood: 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.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.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/arashpartow/exprtk)