0
/ 100
Good community traction and solid fundamentals. Nearly in the top tier.
The C++ Standard Library for Parallelism and Concurrency
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
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 4README12pt
Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
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
58
README is present.
README documents how to install the project.
CONTRIBUTING guide found.
Licensed under BSL-1.0.
Engineering
84
CI is configured (.github/workflows/build-and-test.yml).
Test files detected (cmake/tests).
Lockfile present (tools/perftests_ci/requirements.txt). Installs are reproducible.
Linter or formatter configured (.editorconfig).
Issue or PR templates present.
Project health
100
Dependency manifest found (tools/perftests_ci/requirements.txt).
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)
- 546Forks
- 56Releaseslatest 8y ago
Community
- -Community health
- -authors own >50% of commits
- 2,865Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 130Open issues
Repository files28 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/build-and-test.yml).Good: Dependabot configured for github-actions.Good: Issue or PR templates present.Good: Security policy present.
- .jenkins
- cmakeGood: Test files detected (cmake/tests).
- components
- docs
- examples
- init
- libs
- test_package
- tests
- toolsGood: Lockfile present (tools/perftests_ci/requirements.txt). Installs are reproducible.Good: Environment pinned via tools/docker/Dockerfile.Good: Dependency manifest found (tools/perftests_ci/requirements.txt).
- wrap
- .clang-format
- .clang-tidy
- .cmake-format.py
- .codacy.yml
- .conanignore
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- CITATION.cff
- CMakeLists.txt
- CMakePresets.json
- conanfile.py
- CTestConfig.cmake
- hpx.spdx
- LICENSE_1_0.txt
- README.rstGood: 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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/thehpxproject/hpx)