83
/ 100
A top-tier open source project. Docs, tests, and CI are all in excellent shape.
Self-hosted game stream host for Moonlight.
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 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
88
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under GPL-3.0.
Engineering
78
CI is configured (.github/workflows/ci-archlinux.yml).
Test files detected (tests).
Lockfile present (package-lock.json). Installs are reproducible.
Linter or formatter configured (.prettierrc.json).
Issue or PR templates present.
Project health
100
Dependency manifest found (package.json).
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)
- 2,088Forks
- 46Releaseslatest 5y ago
Community
- 87% - GoodCommunity health
- 2 bus factorauthors own >50% of commits
- 39,060Watchers
Responsiveness
- 15hMedian issue response
- 1d 2hMedian PR merge time
- 125Open issues
Repository files39 root entries
- .githubGood: CI is configured (.github/workflows/ci-archlinux.yml).Good: Dependabot configured for gitsubmodule.Good: Issue or PR templates present.
- .run
- cmake
- docker
- docsGood: 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.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- gh-pages-template
- packaging
- scripts
- src
- src_assets
- testsGood: Test files detected (tests).
- third-party
- tools
- .clang-format
- .dockerignore
- .gitattributes
- .gitignoreGood: .gitignore present.
- .gitmodules
- .prettierrc.jsonGood: Linter or formatter configured (.prettierrc.json).
- .readthedocs.yaml
- .rstcheck.cfg
- .sonarcloud.properties
- AGENTS.md
- CMakeLists.txt
- crowdin.yml
- DOCKER_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.
- LICENSEGood: Licensed under GPL-3.0.
- NOTICE
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- pyproject.toml
- README.md
- renovate.json
- sonar-project.properties
- sunshine.ico
- sunshine.png
- sunshine.svg
- uv.lock
- vite.config.js
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/lizardbyte/sunshine)