62
/ 100
Strong community interest, but tests, CI, or docs need work.
v2ray subscription links
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (85).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add automated tests. They prove the code works and give contributors confidence to make changes.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
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
82
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 documents how to install the project.
README is present.
Licensed under GPL-3.0.
Engineering
40
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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/linter.yml).
Lockfile present (package-lock.json). Installs are reproducible.
Rust linting configured (.prettierrc.json).
Project health
86
Dependency manifest found (Cargo.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 202 / 509Commits (30d / 90d)
- 298Forks
- 0Releases
Community
- 42% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 1,215Watchers
Responsiveness
- -Median issue response
- <1hMedian PR merge time
- 0Open issues
Repository files20 root entries
- .githubGood: CI is configured (.github/workflows/linter.yml).
- boringtun-boringtun-cli-0.5.2
- DNS over HTTPS
- edge
- hiddify
- real address generator
- sub
- .gitignoreGood: .gitignore present.
- .prettierignore
- .prettierrc.jsonGood: Rust linting configured (.prettierrc.json).
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- Cloudflare-IPs.json
- ESET-CODES.md
- eslint.config.js
- LICENSEGood: Licensed under GPL-3.0.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.json
- 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.Good: README documents how to install the project.Good: README documents how to run the project.
- sing-box.json
- warp.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/nirevil/vless)