Strong community interest, but tests, CI, or docs need work.
Practical and Powerful wayland compositor (dwm but wayland)
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 Other.
Engineering
29
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 dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
CI is configured (.github/workflows/generate-nix-options-docs.yml).
Issue or PR templates present.
Project health
68
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
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)
- 192Forks
- 74Releaseslatest 1y ago
Community
- —Community health
- —authors own >50% of commits
- 3,130Watchers
Responsiveness
- 1hMedian issue response
- <1hMedian PR merge time
- 196Open issues
Repository files22 root entries
- .githubGood: CI is configured (.github/workflows/generate-nix-options-docs.yml).Good: Issue or PR templates present.
- assets
- docs
- mmsg
- nix
- protocols
- src
- .clang-format
- .gitignoreGood: .gitignore present.
- flake.lock
- flake.nix
- format.sh
- LICENSEGood: Licensed under Other.
- LICENSE.dwl
- LICENSE.dwm
- LICENSE.sway
- LICENSE.tinywl
- LICENSE.wlroots
- mangowm.scm
- meson_options.txt
- meson.build
- 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.