0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Qualitative data analysis for text, images, audio, video. Cross platform. Python 3.12 or newer and PyQt6.
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
Add CI/build status badges from shields.io or your CI provider to signal project health.
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
90
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under LGPL-3.0.
Engineering
71
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.
Lockfile present (requirements.txt). Installs are reproducible.
CI is configured (.github/workflows/python-app.yml).
Test files detected (tests).
Issue or PR templates present.
Project health
100
Dependency manifest found (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)
- 131Forks
- 23Releaseslatest 5y ago
Community
- -Community health
- -authors own >50% of commits
- 632Watchers
Responsiveness
- 5hMedian issue response
- <1hMedian PR merge time
- 22Open issues
Repository files28 root entries
- .githubGood: CI is configured (.github/workflows/python-app.yml).Good: Issue or PR templates present.
- doc
- Examples
- icons
- other_languages
- src
- testsGood: Test files detected (tests).
- .gitignoreGood: .gitignore present.
- 2023QualCoder.code-workspace
- CITATION.cff
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.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).Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- install_fedora_DONT_USE_KEEPING_JUST_IN_CASE.sh
- LICENSE.txtGood: Licensed under LGPL-3.0.
- mac_build-dmg.sh
- MANIFEST.in
- QC_Logo.ico
- qualcoder_onefile.spec
- qualcoder.png
- qualcoder.spec
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.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.
- rebuild_lang.py
- rebuild_ui.py
- Release_notes.md
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.Good: Dependency manifest found (requirements.txt).
- ROADMAP.md
- run_from_source_Ubuntu.sh
- run_from_source_Windows.bat
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/ccbogel/qualcoder)