0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Open source XMLTV data for UK free-to-air TV channels and radio stations
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 step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
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
86
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README documents how to install the project.
README is present.
Licensed under GPL-3.0.
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.
CI is configured (.github/workflows/build_epg.yml).
Lockfile present (requirements.txt). Installs are reproducible.
Test files detected (pytest.ini).
Issue or PR templates present.
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)
- 21Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 176Watchers
Responsiveness
- 2hMedian issue response
- <1hMedian PR merge time
- 4Open issues
Repository files15 root entries
- .githubGood: CI is configured (.github/workflows/build_epg.yml).Good: Issue or PR templates present.
- src
- tests
- wiki
- .gitignoreGood: .gitignore present.
- channels.json
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- epg.xml
- jsontomd.py
- LICENSEGood: Licensed under GPL-3.0.
- main.py
- 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.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-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/dp247/freeview-epg)