Getting noticed, but rough fundamentals could turn visitors away.
🛡️ Автоматический сборщик MTProto‑прокси с уникальной фильтрацией «Умный комбайн» для автоматического сбора, анализа и фильтрации MTProto‑прокси. Отделяет **"золотые" прокси**, маскирующиеся под Yandex, VK, Gosuslugi и другие популярные RU‑сервисы (Fake‑TLS), от обычных.
Documentation
63
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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.
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/update.yml).
Lockfile present (requirements.txt). Installs are reproducible.
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)
- 57Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 848Watchers
Responsiveness
- 2d 19hMedian issue response
- —Median PR merge time
- 14Open issues
Repository files18 root entries
- .githubGood: CI is configured (.github/workflows/update.yml).
- verified
- .gitignoreGood: .gitignore present.
- config.yml
- domains.txt
- main.py
- mobile.html
- ping_history.json
- proxy_all.txt
- proxy_eu.txt
- proxy_list.txt
- proxy_ru.txt
- 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.
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.Good: Dependency manifest found (requirements.txt).
- socks5.txt
- tcp16.json
- telegram-proxy-collector.jpg
- whitelist_sni.txt