iptv-org/database

0

/ 100

Documentation77
Engineering84
Health86
JavaScript1,485Unlicense1d ago
Grade a repo

Good community traction and solid fundamentals. Nearly in the top tier.

User editable database for TV channels.

Documentation

77

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt85

README is present.

Contributing guide5pt85

Contributing guide is detailed and thorough.

License6pt100

Licensed under Unlicense.

Engineering

84

CI/CD14pt57

CI is configured (.github/workflows/check.yml).

Reproducibility6pt70

Lockfile present (package-lock.json). Installs are reproducible.

Tests18pt100

Test files detected (tests).

Linting and formatting5pt100

Linter or formatter configured (.prettierrc.js).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

86

Dependency manifest6pt55

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 569
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 1,485
    Watchers

Responsiveness

  • 3h
    Median issue response
  • <1h
    Median PR merge time
  • 17
    Open issues
Repository files15 root entries
  • .github
    Good: Code of conduct present.
    Good: CI is configured (.github/workflows/check.yml).
    Good: Issue or PR templates present.
  • .husky
  • .readme
    Good: 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
  • tests
    Good: Test files detected (tests).
  • .gitignore
    Good: .gitignore present.
  • .prettierrc.js
    Good: Linter or formatter configured (.prettierrc.js).
  • CONTRIBUTING.md
    Good: 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
  • LICENSE
    Good: Licensed under Unlicense.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • README.md
  • tsconfig.json