0
/ 100
Strong community interest, but tests, CI, or docs need work.
๐ช Windows & Linux userspace emulator
Documentation
82
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 documents how to install the project.
README is present.
Licensed under GPL-2.0.
Engineering
46
No tests detected anywhere in the repository.
โ Add automated tests. They prove the code works and give contributors confidence to make changes.
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/build-push.yml).
Lockfile present (page/package-lock.json). Installs are reproducible.
Linter or formatter configured (page/.prettierrc).
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)
- 202Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 3,228Watchers
Responsiveness
- 15d 1hMedian issue response
- <1hMedian PR merge time
- 26Open issues
Repository files20 root entries
- .githubGood: CI is configured (.github/workflows/build-push.yml).Good: Dependabot covers 5 ecosystems (gitsubmodule, github-actions, pip, npm, cargo). Dependencies stay current.
- cmake
- deps
- docs
- examples
- pageGood: Linter or formatter configured (page/.prettierrc).Good: Lockfile present (page/package-lock.json). Installs are reproducible.
- src
- .clang-format
- .clang-format-ignore
- .clang-tidy
- .gitignoreGood: .gitignore present.
- .gitmodules
- AGENTS.md
- CLAUDE.md
- CMakeLists.txt
- CMakePresets.json
- LICENSEGood: Licensed under GPL-2.0.
- MANIFEST.in
- 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.Good: README has code examples.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.