0
/ 100
Real traction, but rough engineering makes it hard for contributors to trust.
Guide by Example
Documentation
59
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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 is present.
README documents how to install the project.
Engineering
0
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
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.
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.
Project health
59
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.
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 184Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 2,888Watchers
Responsiveness
- 17hMedian issue response
- 16hMedian PR merge time
- 25Open issues
Repository files58 root entries
- _knowledge-base
- arch_linux_host_install
- arch_raspberry_pi
- audiobookshelf
- beginners-speedrun-selfhosting
- bookstack
- borg_backup
- caddy_v2
- checkmk
- crafty
- ddclient
- disk_NAS_bench_Fio
- dnsmasq
- docker-basics-and-troubleshoot
- esxi
- free_cloud_hosting_VPS
- frigate
- gatus
- get_good_linux_terminal
- gotify-ntfy-signal
- home_assistant
- homer
- immich
- jellyfin
- kopia_backup
- lubelog
- mail-archiver
- mealie
- meshcrentral
- mikrotik
- minecraft
- mounting_network_share_linux
- network-knowledge-base
- nextcloud
- NUT-Network UPS Tools
- opnsense
- phpipam
- port_forwarding_guide
- portainer
- prometheus_grafana_loki
- proxmox
- qbittorrent
- rustdesk
- snipeit
- squid
- syncthing
- trueNASscale
- umami
- unifi
- uptime-kuma
- vaultwarden
- watchtower
- watchyourlan
- wg-easy
- windows_package_managers
- wireguard
- zammad
- 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.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.Good: README documents how to run the project.