65
/ 100
Solid engineering. The biggest lever is CI.
A GUI client for Windows, Linux and macOS, support Xray and sing-box and others
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
69
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-3.0.
Engineering
66
No dependency lockfile found (−70 pts).
→ Enable and commit packages.lock.json so NuGet restores are repeatable.
CI is configured (.github/workflows/build-all.yml).
Test files detected (v2rayN/ServiceLib.Tests/CoreConfig/Context/CoreConfigContextBuilderTests.cs).
.NET formatting configured (.editorconfig).
Issue or PR templates present.
Project health
100
Dependency manifest found (v2rayN/AmazTool/AmazTool.csproj).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 54 / 180Commits (30d / 90d)
- 15,587Forks
- 328Releaseslatest 6y ago
Community
- 42% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 112,243Watchers
Responsiveness
- 13hMedian issue response
- 3hMedian PR merge time
- 10Open issues
Repository files15 root entries
- .githubGood: CI is configured (.github/workflows/build-all.yml).Good: Dependabot covers 2 ecosystems (github-actions, nuget). Dependencies stay current.Good: Issue or PR templates present.
- v2rayNGood: Test files detected (v2rayN/ServiceLib.Tests/CoreConfig/Context/CoreConfigContextBuilderTests.cs).Good: Dependency manifest found (v2rayN/AmazTool/AmazTool.csproj).
- .editorconfigGood: .NET formatting configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .gitmodules
- LICENSEGood: Licensed under GPL-3.0.
- package-debian-loong.sh
- package-debian-riscv.sh
- package-debian.sh
- package-osx.sh
- package-rhel-loong.sh
- package-rhel-riscv.sh
- package-rhel.sh
- 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.Good: README includes status badges.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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/2dust/v2rayn)