0
/ 100
Getting noticed, but rough fundamentals could turn visitors away.
Extra Packages for OpenWrt 24.10 & 25.12
Documentation
11
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
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.
Engineering
11
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.
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-packages.yml).
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)
- 62Forks
- 1Releaseslatest 3mo ago
Community
- -Community health
- -authors own >50% of commits
- 127Watchers
Responsiveness
- 2hMedian issue response
- <1hMedian PR merge time
- 1Open issues
Repository files48 root entries
- .githubGood: CI is configured (.github/workflows/build-packages.yml).
- chinadns-ng
- dae
- daed
- dns2socks
- dns2socks-rust
- dns2tcp
- geoview
- hysteria
- ipt2socks
- kcptun
- lua-neturl
- luci-app-dae
- luci-app-daed
- luci-app-homeproxy
- luci-app-momo
- luci-app-nikki
- luci-app-openclash
- luci-app-passwall
- luci-app-passwall2
- luci-app-ssr-plus
- microsocks
- mihomo-alpha
- mihomo-meta
- momo
- naiveproxy
- nikki
- pdnsd
- redsocks2
- shadow-tls
- shadowsocks-libev
- shadowsocks-rust
- shadowsocksr-libev
- simple-obfs
- sing-box
- tcping
- trojan
- trojan-plus
- tuic-client
- v2ray-core
- v2ray-geodata
- v2ray-plugin
- vmlinux-btf
- xray-core
- xray-plugin
- patch-luci-app-passwall.patch
- patch-luci-app-ssr-plus.patch
- README.mdGood: README is present.Issue: README is very short (−20 pts). 400+ characters earns +10 pts; 1,500+ earns +20 pts.Fix: Add an Overview, Install, Usage, and Contributing section at minimum.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.Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.