whyboris/video-hub-app

0

/ 100

Documentation77
Engineering49
Health100
TypeScript704MIT1d ago
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

Official repository for Video Hub App

Documentation

77

Contributing guide5pt30

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.

README12pt75

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

49

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

CI/CD14pt57

CI is configured (.github/workflows/codeql-analysis.yml).

Reproducibility6pt80

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

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

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)
  • 204
    Forks
  • 8
    Releaseslatest 3y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 704
    Watchers

Responsiveness

  • 20h
    Median issue response
  • 19h
    Median PR merge time
  • 140
    Open issues
Repository files28 root entries
  • .github
    Good: CI is configured (.github/workflows/codeql-analysis.yml).
    Good: Issue or PR templates present.
  • .vscode
  • bin
  • build
  • demo
  • i18n
  • interfaces
  • node
  • remote
  • src
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .eslintrc.json
  • .gitignore
    Good: .gitignore present.
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • .stylelintrc
  • angular.json
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • electron-builder.json
  • LICENSE
    Good: Licensed under MIT.
  • main.ts
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • README.md
    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.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • tsconfig-serve.json
  • tsconfig.base.json
  • tsconfig.json
  • tsconfig.worker.json