0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
Windows-приложение для удобного управления zapret и tg-ws-proxy из единого интерфейса.
Documentation
93
CONTRIBUTING guide found.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
30
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 configured.
→ Add [tool.ruff] to pyproject.toml. Ruff handles linting and formatting in one tool and replaces flake8, isort, and black.
No dependency lockfile found (−70 pts).
→ Commit poetry.lock, uv.lock, pdm.lock, Pipfile.lock, conda-lock.yml, or another lockfile for your Python dependency manager.
CI is configured (.github/workflows/ci.yml).
Issue or PR templates present.
Project health
96
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)
- 8Forks
- 18Releaseslatest 2mo ago
Community
- -Community health
- -authors own >50% of commits
- 245Watchers
Responsiveness
- 2hMedian issue response
- <1hMedian PR merge time
- 2Open issues
Repository files16 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- assets
- docs
- installer
- packaging
- runtimeGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: Environment pinned via runtime/tg-ws-proxy/Dockerfile.Good: Issue or PR templates present.
- sample_data
- scripts
- src
- ui_assets
- _refresh_release.py
- .gitignoreGood: .gitignore present.
- donations.md
- LICENSEGood: Licensed under MIT.
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- 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.