0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
A distributed scheduling system for HPC and AI workloads
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 C (77).
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
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
63
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under Other.
Engineering
54
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 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 (.github/workflows/build.yaml).
Lockfile present (docs/requirements.txt). Installs are reproducible.
Test files detected (test).
Project health
100
Dependency manifest found (docs/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)
- 36Forks
- 5Releaseslatest 9mo ago
Community
- -Community health
- -authors own >50% of commits
- 139Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 73Open issues
Repository files25 root entries
- .devin
- .githubGood: CI is configured (.github/workflows/build.yaml).
- CMakeModule
- dependencies
- docsGood: Lockfile present (docs/requirements.txt). Installs are reproducible.Good: Dependency manifest found (docs/requirements.txt).
- etc
- protos
- scripts
- src
- testGood: Test files detected (test).
- .clang-format
- .clang-format-proto
- .clang-tidy
- .coderabbit.yaml
- .gdbinit
- .gitattributes
- .gitignoreGood: .gitignore present.
- .readthedocs.yaml
- CMakeLists.txt
- CMakePresets.json
- LICENSEGood: Licensed under Other.
- mkdocs.yaml
- README_EN.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.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.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.
- README.md
- VERSION
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/pkuhpc/cranesched)