0
/ 100
Good community traction and solid fundamentals. Nearly in the top tier.
User editable database for TV channels.
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 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.
- 4CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
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
77
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Contributing guide is detailed and thorough.
Licensed under Unlicense.
Engineering
84
CI is configured (.github/workflows/check.yml).
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (tests).
Linter or formatter configured (.prettierrc.js).
Issue or PR templates present.
Project health
86
Dependency manifest found (package.json).
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)
- 569Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 1,485Watchers
Responsiveness
- 3hMedian issue response
- <1hMedian PR merge time
- 17Open issues
Repository files15 root entries
- .githubGood: Code of conduct present.Good: CI is configured (.github/workflows/check.yml).Good: Issue or PR templates present.
- .husky
- .readmeGood: 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.Good: README includes status badges.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Good: README documents how to run the project.
- data
- scripts
- testsGood: Test files detected (tests).
- .gitignoreGood: .gitignore present.
- .prettierrc.jsGood: Linter or formatter configured (.prettierrc.js).
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Good: Contributing guide describes code style expectations.Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- eslint.config.mjs
- LICENSEGood: Licensed under Unlicense.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- README.md
- tsconfig.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/iptv-org/database)