Getting noticed, but rough fundamentals could turn visitors away.
Documentation
22
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
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.
Licensed under LGPL-3.0.
Engineering
47
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.
Go module found but no *_test.go files detected.
→ Add *_test.go files alongside your packages and run `go test ./...`.
CI is configured (.github/workflows/main.yml).
Lockfile present (go.sum). Installs are reproducible.
Formatting enforced (gofmt (built into Go toolchain)).
Project health
84
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Dependency manifest found (go.mod).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 301Forks
- 61Releaseslatest 1y ago
Community
- —Community health
- —authors own >50% of commits
- 445Watchers
Responsiveness
- 10d 21hMedian issue response
- 8hMedian PR merge time
- 0Open issues
Repository files11 root entries
- .githubGood: CI is configured (.github/workflows/main.yml).
- assets
- .gitignoreGood: .gitignore present.
- gen_assets.sh
- go.modGood: Dependency manifest found (go.mod).
- go.sumGood: Lockfile present (go.sum). Installs are reproducible.
- libv2ray_android.go
- libv2ray_certSha256.go
- libv2ray_main.go
- LICENSEGood: Licensed under LGPL-3.0.
- 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.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.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.