Getting noticed, but rough fundamentals could turn visitors away.
CachyOS kernel for NixOS
Documentation
58
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under GPL-2.0.
Engineering
25
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/auto-update.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)
- 23Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 611Watchers
Responsiveness
- 6hMedian issue response
- 3hMedian PR merge time
- 7Open issues
Repository files11 root entries
- .githubGood: CI is configured (.github/workflows/auto-update.yml).Good: Dependabot configured for github-actions.Good: Issue or PR templates present.
- kernel-cachyos
- zfs-cachyos
- .gitignoreGood: .gitignore present.
- default.nix
- flake.lock
- flake.nix
- helpers.nix
- LICENSEGood: Licensed under GPL-2.0.
- loadPackages.nix
- README.mdGood: README is present.Good: README is well structured with multiple sections.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.Good: README has code examples.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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Good: README documents how to run the project.