Real traction, but rough engineering makes it hard for contributors to trust.
๐กIPTV่็ฎๆบๆถ้๏ผๆฏ4ๅฐๆถๆดๆฐ๏ผ๏ผ
Documentation
56
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.
No install instructions found in the README (โ45 pts).
โ Add a section showing how to install dependencies.
README is present.
Licensed under Apache-2.0.
Engineering
11
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 config found.
โ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
No dependency lockfile found (โ70 pts).
โ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
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/iptv.yml).
Project health
48
No dependency manifest detected at root.
โ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
No .gitignore found (โ60 pts).
โ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- โCommits (30d / 90d)
- 298Forks
- 0Releases
Community
- โCommunity health
- โauthors own >50% of commits
- 1,733Watchers
Responsiveness
- 14hMedian issue response
- โMedian PR merge time
- 0Open issues
Repository files6 root entries
- .githubGood: CI is configured (.github/workflows/iptv.yml).
- best_sorted.m3u
- best_sorted.m3u8
- DISCLAIMER.md
- LICENSEGood: Licensed under Apache-2.0.
- 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.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.Good: README documents how to run the project.