Popular for its size, but the engineering basics lag behind the interest.
Unraid Web UI
Documentation
53
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 documents how to install the project.
README is present.
A license file is present.
Engineering
58
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 composer.lock so Composer installs are repeatable.
CI is configured (.github/workflows/pr-plugin-build.yml).
Test files detected (emhttp/plugins/dynamix/agents/tests).
Issue or PR templates present.
Project health
100
Dependency manifest found (emhttp/plugins/dynamix.vm.manager/novnc/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)
- 98Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 248Watchers
Responsiveness
- 2d 14hMedian issue response
- 11hMedian PR merge time
- 40Open issues
Repository files10 root entries
- .githubGood: CI is configured (.github/workflows/pr-plugin-build.yml).
- .vscode
- emhttpGood: A license file is present.Good: Test files detected (emhttp/plugins/dynamix/agents/tests).Good: Issue or PR templates present.Good: Dependency manifest found (emhttp/plugins/dynamix.vm.manager/novnc/package.json).
- etc
- sbin
- share
- ungrub
- .gitattributes
- .gitignoreGood: .gitignore present.
- README.mdGood: README is present.Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.Good: README documents how to install the project.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.