Getting noticed, but rough fundamentals could turn visitors away.
tv channels & sporting events
Documentation
41
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 Unlicense.
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 configured.
→ Add [tool.ruff] to pyproject.toml. Ruff handles linting and formatting in one tool and replaces flake8, isort, and black.
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/epg.yml).
Lockfile present (uv.lock). Installs are reproducible.
Project health
91
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)
- 43Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 192Watchers
Responsiveness
- 3hMedian issue response
- <1hMedian PR merge time
- 0Open issues
Repository files8 root entries
- .githubGood: CI is configured (.github/workflows/epg.yml).
- M3U8
- .gitignoreGood: .gitignore present.
- health.sh
- LICENSEGood: Licensed under Unlicense.
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- readme.mdGood: README is present.Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.Good: README has code examples.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.
- uv.lockGood: Lockfile present (uv.lock). Installs are reproducible.