livekit/egress
Grade a repo

0

/ 100

GradeB

Polished and well engineered. Punching above its star count.

Top 20% of 5,156 graded repos

Export and record WebRTC sessions and tracks

Documentation78
Engineering86
Health100
Go347Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

9 to address
  1. 1
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

  4. 4
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

78

Contributing guide5pt0

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.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

86

CI/CD14pt57

CI is configured (.github/workflows/test-cleanup.yaml).

Reproducibility6pt85

Lockfile present (go.sum). Installs are reproducible.

Tests18pt100

Test files detected (build/test).

Linting and formatting5pt100

Formatting enforced (.golangci.yaml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (go.mod).

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)
  • 172
    Forks
  • 22
    Releaseslatest 3y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 347
    Watchers

Responsiveness

  • 4d 19h
    Median issue response
  • 5h
    Median PR merge time
  • 54
    Open issues
Repository files19 root entries
  • .github
    Good: CI is configured (.github/workflows/test-cleanup.yaml).
    Good: Issue or PR templates present.
  • build
    Good: Test files detected (build/test).
    Good: Environment pinned via build/chrome/Dockerfile.
  • cmd
  • pkg
  • template-default
  • template-sdk
  • test
  • version
  • .gitignore
    Good: .gitignore present.
  • .golangci.yaml
    Good: Formatting enforced (.golangci.yaml).
  • bootstrap.sh
  • chrome-sandboxing-seccomp-profile.json
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • magefile.go
  • NOTICE
  • README.md
    Good: 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.
    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.
  • renovate.json
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/livekit/egress)](https://www.repo-grade.com/report/livekit/egress)

More graded Go repos