55
/ 100
Solid engineering. The biggest lever is issue and PR templates.
Aggregates multi-protocol proxy configs from Telegram, base64 subs & SSCONF. Tests them with Xray and Sing-box cores over multiple rounds, filters for security, then delivers ready-to-use Xray, Sing-box, and Clash/Mihomo configs (TLS-fragmented anti-censorship + 25 country-specific configs) via 36 endpoints.
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 lint step to catch style issues automatically.
- 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 MIT.
Engineering
62
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.
Lockfile present (requirements.txt). Installs are reproducible.
Test files detected (tests).
CI is configured (.github/workflows/tests.yml).
Project health
100
Dependency manifest found (requirements.txt).
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)
- 37Forks
- 0Releases
Community
- 42% - WeakCommunity health
- -authors own >50% of commits
- 96Watchers
Responsiveness
- 2d 24hMedian issue response
- -Median PR merge time
- 1Open issues
Repository files21 root entries
- .githubGood: CI is configured (.github/workflows/tests.yml).
- assets
- configs
- flag
- settings
- src
- testsGood: Test files detected (tests).
- .gitignoreGood: .gitignore present.
- install.bat
- install.sh
- LICENSEGood: Licensed under MIT.
- README_CN.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.
- README_FA.md
- README_RU.md
- README_WIZARD_CN.md
- README_WIZARD_EN.md
- README_WIZARD_FA.md
- README_WIZARD_RU.md
- README.md
- requirements-dev.txt
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.Good: Dependency manifest found (requirements.txt).
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/4n0nymou3/multi-proxy-config-fetcher)