0
/ 100
Solid foundation. Invest in docs and CI to grow from here.
Additional command line based tools to help in SonarQube administration tasks
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
76
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.
README is present.
README documents how to install the project.
Licensed under LGPL-3.0.
Engineering
71
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.
Lockfile present (poetry.lock). Installs are reproducible.
CI is configured (.github/workflows/build.yml).
Test files detected (test).
Linter or formatter configured (conf/.flake8).
Project health
100
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)
- 22Forks
- 76Releaseslatest 5y ago
Community
- -Community health
- -authors own >50% of commits
- 66Watchers
Responsiveness
- 7d 18hMedian issue response
- <1hMedian PR merge time
- 27Open issues
Repository files19 root entries
- .claude
- .githubGood: CI is configured (.github/workflows/build.yml).
- .vscode
- cli
- confGood: Linter or formatter configured (conf/.flake8).
- doc
- sonar
- testGood: Test files detected (test).
- .gitignoreGood: .gitignore present.
- CLAUDE.md
- LICENSEGood: Licensed under LGPL-3.0.
- poetry.lockGood: Lockfile present (poetry.lock). Installs are reproducible.
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- 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.Good: README documents how to run the project.
- SECURITY.mdGood: Security policy present.
- sonar-project.properties
- sonar-tools.code-workspace
- sync-issues.properties
- testcloud.xml
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/okorach/sonar-tools)