0
/ 100
Solid early foundation. Docs and CI will help it get noticed.
:robot: MoveIt for ROS 2
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.
- 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
71
README documents how to install the project.
CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README is present.
Licensed under BSD-3-Clause.
Engineering
66
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.
CI is configured (.github/workflows/ci.yaml).
Test files detected (moveit_configs_utils/test).
Issue or PR templates present.
Project health
100
Dependency manifest found (moveit_configs_utils/setup.py).
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)
- 0Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 0Watchers
Responsiveness
- -Median issue response
- <1hMedian PR merge time
- 1Open issues
Repository files29 root entries
- .dockerGood: Environment pinned via .docker/ci-testing/Dockerfile.
- .githubGood: CI is configured (.github/workflows/ci.yaml).Good: Dependabot covers 2 ecosystems (docker, github-actions). Dependencies stay current.Good: Issue or PR templates present.
- doc
- moveit
- moveit_common
- moveit_configs_utilsGood: Test files detected (moveit_configs_utils/test).Good: Dependency manifest found (moveit_configs_utils/setup.py).
- moveit_core
- moveit_kinematics
- moveit_planners
- moveit_plugins
- moveit_py
- moveit_ros
- moveit_runtime
- moveit_setup_assistant
- .clang-format
- .clang-tidy
- .codespell_words
- .dockerignore
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- codecov.yaml
- CONTRIBUTING.mdIssue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- Doxyfile
- LICENSE.txtGood: Licensed under BSD-3-Clause.
- MIGRATION.md
- moveit2.repos
- README.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.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.
- sonar-project.properties
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/kinisi-robotics/moveit2)