mozilla/bugbug
Grade a repo

80

/ 100

GradeB

Good shape overall. A few tweaks would push it into the top tier.

Top 32% of 5,156 graded repos

Platform for Machine Learning projects on Software Engineering

Documentation93
Engineering65
Health98
Python565MPL-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

15 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

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

  3. 3
    CI/CD14pt

    Add `pull_request:` to the workflow `on:` triggers.

  4. 4
    CI/CD14pt

    Add a lint step to catch style issues automatically.

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

93

Contributing guide5pt52

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MPL-2.0.

Engineering

65

Issue and PR templates6pt0

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/CD14pt40

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

Tests18pt85

Test files detected (bugbug/test_scheduling.py).

Linting and formatting5pt100

Linter or formatter configured (.prettierrc).

Reproducibility6pt100

Lockfile present (uv.lock). Installs are reproducible.

Project health

98

Dependency manifest6pt93

Dependency manifest found (pyproject.toml).

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

  • 113 / 346
    Commits (30d / 90d)
  • 336
    Forks
  • 0
    Releases

Community

  • 75% - Good
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 565
    Watchers

Responsiveness

  • 37d 22h
    Median issue response
  • 6h
    Median PR merge time
  • 467
    Open issues
Repository files28 root entries
  • .github
    Good: CI is configured (.github/workflows/comment_resolver.yml).
    Good: Dependabot covers 5 ecosystems (docker, uv, uv, npm, pre-commit). Dependencies stay current.
  • agents
    Good: Environment pinned via agents/autowebcompat-repro/Dockerfile.
  • bugbug
    Good: Test files detected (bugbug/test_scheduling.py).
  • docs
  • functions
  • http_service
  • infra
  • libs
  • notebooks
  • scripts
  • services
  • tests
  • ui
  • .codecov.yml
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • .pre-commit-config.yaml
  • .prettierrc
    Good: Linter or formatter configured (.prettierrc).
  • .taskcluster.yml
  • CITATION.cff
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • docker-compose.yml
  • LICENSE
    Good: Licensed under MPL-2.0.
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • uv.lock
    Good: Lockfile present (uv.lock). Installs are reproducible.
  • VERSION
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/mozilla/bugbug)](https://www.repo-grade.com/report/mozilla/bugbug)

More graded Python repos