56
/ 100
Early-stage engineering. The fastest wins are test coverage and CI.
Android real-time display control software
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 B (83).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add automated tests. They prove the code works and give contributors confidence to make changes.
- 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
80
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
25
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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/macos.yml).
Lockfile present (ci/mac/package/requirements.txt). Installs are reproducible.
Project health
100
Dependency manifest found (ci/mac/package/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
- 11 / 11Commits (30d / 90d)
- 3,653Forks
- 37Releaseslatest 6y ago
Community
- 42% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 30,743Watchers
Responsiveness
- 7d 23hMedian issue response
- <1hMedian PR merge time
- 611Open issues
Repository files15 root entries
- .githubGood: CI is configured (.github/workflows/macos.yml).
- backup
- ciGood: Lockfile present (ci/mac/package/requirements.txt). Installs are reproducible.Good: Dependency manifest found (ci/mac/package/requirements.txt).
- config
- docs
- keymap
- QtScrcpy
- screenshot
- .clang-format
- .gitignoreGood: .gitignore present.
- .gitmodules
- CMakeLists.txt
- LICENSEGood: Licensed under Apache-2.0.
- README_zh.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.
- README.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/barry-ran/qtscrcpy)