0
/ 100
Solid engineering. The main gap is visibility.
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.
- 4README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
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
47
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
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 is present.
Licensed under MIT.
Engineering
88
Lockfile present (poetry.lock). Installs are reproducible.
Test files detected (pytest.ini).
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (.flake8).
Issue or PR templates present.
Project health
82
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Dependency manifest found (pyproject.toml).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 8Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 0Open issues
Repository files28 root entries
- .devcontainerGood: Environment pinned via .devcontainer/Dockerfile.
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Issue or PR templates present.
- .vscode
- ip
- iptv
- m3u
- rtp
- tests
- txt
- .flake8Good: Linter or formatter configured (.flake8).
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- .python-version
- e.xml
- epg.py
- iptv_unicom.py
- iptv.py
- iptv.sh
- LICENSEGood: Licensed under MIT.
- main.py
- mypy.ini
- poetry.lockGood: Lockfile present (poetry.lock). Installs are reproducible.
- poetry.toml
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- pytest.iniGood: Test files detected (pytest.ini).
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Good: README links to a live demo or deployed app.Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.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.
- requirements.txt
- tox.ini
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/xudagege/xingxing)