0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
A set of examples based on verl for end-to-end RL training recipes.
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
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
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
77
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README is present.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
70
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/pre-commit.yml).
Test files detected (async_flow/tests).
Lockfile present (async_flow/requirements.txt). Installs are reproducible.
Linter or formatter configured ([tool.ruff] / [tool.black] in pyproject.toml).
Project health
96
Dependency manifest found (pyproject.toml).
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)
- 139Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 298Watchers
Responsiveness
- 1d 9hMedian issue response
- 1d 23hMedian PR merge time
- 38Open issues
Repository files38 root entries
- .githubGood: CI is configured (.github/workflows/pre-commit.yml).
- async_flowGood: Test files detected (async_flow/tests).Good: Lockfile present (async_flow/requirements.txt). Installs are reproducible.
- atropos
- char_count
- collabllm
- dance_grpo
- dapo
- deepeyes
- entropy
- fapo
- flowrl
- genrm_remote
- gkd
- gvpo
- infigui-g1
- langgraph_agent
- low_precision
- minicpmo
- nemo_gym
- open_math_reasoning
- partial_rollout
- prime
- qat
- r1
- rep_exp
- retool
- specRL
- spin
- spoGood: Environment pinned via spo/environment.yml.
- sppo
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- change.md
- CODEOWNERS
- install_verl.sh
- LICENSEGood: Licensed under Apache-2.0.
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README.mdGood: README is present.Good: README is well structured with multiple sections.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.Good: README has code examples.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/verl-project/verl-recipe)