0
/ 100
Lots of room to improve. Start with a README and CI.
GPU utils to use A2A propagators in isospin-breaking corrections to pi-pi scattering
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 add 30 points.
See your top fixesTop 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
If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
- 3README12pt
Add a README.md describing what the project does, how to install it, and how to run it.
- 4Install and run instructions9pt
Add a section showing how to install dependencies.
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
0
No README found in the repository.
→ Add a README.md describing what the project does, how to install it, and how to run it.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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.
Engineering
29
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
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.
Test files detected (old_stuff/GPU-nvlink-tests/test).
Project health
57
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.
.gitignore present.
Actively maintained (pushed within 3 months).
Repository has a description.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 0Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 0Open issues
Repository files20 root entries
- autocontraction-symbolic-manipulation
- autocontraction-symbolic-manipulation-fewer-FFTsIssue: Build artifacts or local files may be committed (autocontraction-symbolic-manipulation-fewer-FFTs/__pycache__/optimize_products_fewer_FFT.cpython-314.pyc) (−40 pts).Fix: Remove them and add to .gitignore.
- benchmarking_fft
- old_stuffGood: Test files detected (old_stuff/GPU-nvlink-tests/test).
- .gitignoreGood: .gitignore present.
- A2A_Mat_Vec_util.h
- AGENTS.md
- CLAUDE.md
- compile-matrix-vector.sh
- compile-phtn.sh
- disconnected_test.cu
- FFT-test.cu
- FFttest
- GPU-envionrment.sh
- IV-photon-props.h
- load_data.h
- load-data-test.cu
- matrix-vector-test.cu
- mpi-perlmutter-run-cmd.sh
- prop-test.cc
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/erikll579/a2a-utils-pipi-scattering)