Strong community interest, but docs and engineering haven't caught up to the hype.

Android real-time display control software

Documentation

80

Contributing guide5pt25

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.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

25

Tests18pt0

No tests detected anywhere in the repository.

Add automated tests. They prove the code works and give contributors confidence to make changes.

Linting and formatting5pt0

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.

Issue and PR templates6pt0

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/CD14pt57

CI is configured (.github/workflows/macos.yml).

Reproducibility6pt70

Lockfile present (ci/mac/package/requirements.txt). Installs are reproducible.

Project health

95

Activity5pt80

Actively maintained (pushed within 3 months).

Dependency manifest6pt100

Dependency manifest found (ci/mac/package/requirements.txt).

Repository metadata5pt100

Repository has a description.

Housekeeping3pt100

.gitignore present.

Repository files15 root entries
  • .github
    Good: CI is configured (.github/workflows/macos.yml).
  • backup
  • ci
    Good: 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
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • CMakeLists.txt
  • LICENSE
    Good: Licensed under Apache-2.0.
  • README_zh.md
    Good: 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