76
/ 100
Solid engineering. The biggest lever is setup instructions.
🔒 Free V2Ray configs auto-updated every 15m | VLESS, VMess, Trojan, Shadowsocks, Hysteria2, TUIC, Reality, WireGuard | subscription link | bypass censorship | Compatible with v2rayNG, Hiddify, NekoRay, NekoBox, v2rayN, Clash Meta, Shadowrocket | xray-core | iran | free vpn | @Raydikalx
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
71
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
Contributing guide is detailed and thorough.
README is present.
Licensed under MIT.
Engineering
74
CI is configured (.github/workflows/aggregate.yml).
Test files detected (scripts/test_pipeline.py).
Lockfile present (requirements.txt). Installs are reproducible.
Linter or formatter configured ([tool.ruff] / [tool.black] in pyproject.toml).
Issue or PR templates present.
Project health
86
Dependency manifest found (pyproject.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
- -Commits (30d / 90d)
- 40Forks
- 2Releaseslatest 1mo ago
Community
- 100% - GoodCommunity health
- -authors own >50% of commits
- 626Watchers
Responsiveness
- 2d 11hMedian issue response
- <1hMedian PR merge time
- 0Open issues
Repository files33 root entries
- .githubGood: CI is configured (.github/workflows/aggregate.yml).Good: Dependabot covers 2 ecosystems (pip, github-actions). Dependencies stay current.Good: Issue or PR templates present.
- all
- archive
- assets
- Countries
- dashboard-src
- docs
- fast
- heavy
- light
- protocols
- scriptsGood: Test files detected (scripts/test_pipeline.py).
- secure
- verified
- .gitignoreGood: .gitignore present.
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- GOVERNANCE.md
- health.json
- index.json
- LICENSEGood: Licensed under MIT.
- PHASE_A_REPORT.md
- PHASE_G_REPORT.md
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README_FA.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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- README_RU.md
- README_ZH.md
- README.md
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.
- SECURITY.mdGood: Security policy present.
- state.json
- SUPPORT.md
- top100.txt
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/0xradikal/free-v2ray-configs)