Strong community interest, but tests, CI, or docs need work.
Free vless-vmess-shadowsocks-trojan-xray-V2ray Configs Updating Every 5 minutes
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
20
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 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/main.yml).
Lockfile present (Files/requirements.txt). Installs are reproducible.
Project health
91
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
Dependency manifest found (Files/requirements.txt).
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)
- 430Forks
- 1Releaseslatest 11mo ago
Community
- —Community health
- —authors own >50% of commits
- 3,094Watchers
Responsiveness
- 4d 17hMedian issue response
- 7d 12hMedian PR merge time
- 31Open issues
Repository files76 root entries
- .githubGood: CI is configured (.github/workflows/main.yml).
- Base64
- FilesGood: Lockfile present (Files/requirements.txt). Installs are reproducible.Good: Dependency manifest found (Files/requirements.txt).
- Splitted-By-Protocol
- All_Configs_base64_Sub.txt
- All_Configs_Sub.txt
- LICENSEGood: Licensed under GPL-3.0.
- 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.
- Sub1.txt
- Sub10.txt
- Sub11.txt
- Sub12.txt
- Sub13.txt
- Sub14.txt
- Sub15.txt
- Sub16.txt
- Sub17.txt
- Sub18.txt
- Sub19.txt
- Sub2.txt
- Sub20.txt
- Sub21.txt
- Sub22.txt
- Sub23.txt
- Sub24.txt
- Sub25.txt
- Sub26.txt
- Sub27.txt
- Sub28.txt
- Sub29.txt
- Sub3.txt
- Sub30.txt
- Sub31.txt
- Sub32.txt
- Sub33.txt
- Sub34.txt
- Sub35.txt
- Sub36.txt
- Sub37.txt
- Sub38.txt
- Sub39.txt
- Sub4.txt
- Sub40.txt
- Sub41.txt
- Sub42.txt
- Sub43.txt
- Sub44.txt
- Sub45.txt
- Sub46.txt
- Sub47.txt
- Sub48.txt
- Sub49.txt
- Sub5.txt
- Sub50.txt
- Sub51.txt
- Sub52.txt
- Sub53.txt
- Sub54.txt
- Sub55.txt
- Sub56.txt
- Sub57.txt
- Sub58.txt
- Sub59.txt
- Sub6.txt
- Sub60.txt
- Sub61.txt
- Sub62.txt
- Sub63.txt
- Sub64.txt
- Sub65.txt
- Sub66.txt
- Sub67.txt
- Sub68.txt
- Sub7.txt
- Sub8.txt
- Sub9.txt