automattic/jetpack
Grade a repo

0

/ 100

GradeB

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

Top 32% of 5,156 graded repos

Security, performance, marketing, and design tools — Jetpack is made by WordPress experts to make WP sites safer and faster, and help you grow your traffic.

Documentation92
Engineering66
Health94
PHP1,823Other1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

11 to address
  1. 1
    Tests18pt

    Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".

  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 `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

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

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

92

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt92

Contributing guide is detailed and thorough.

License6pt100

Licensed under Other.

Engineering

66

Tests18pt35

Test files detected (projects/github-actions/pr-is-up-to-date/tests).

CI/CD14pt72

CI is configured (.github/workflows/build-docker-monorepo.yml).

Reproducibility6pt80

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

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Dependency manifest6pt82

Dependency manifest found (composer.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)
  • 883
    Forks
  • 344
    Releaseslatest 12y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 1,823
    Watchers

Responsiveness

  • 23h
    Median issue response
  • 2d 13h
    Median PR merge time
  • 2,648
    Open issues
Repository files39 root entries
  • .agents
  • .claude
  • .cursor
  • .github
    Good: CI is configured (.github/workflows/build-docker-monorepo.yml).
    Good: Issue or PR templates present.
    Good: .gitignore present.
  • .husky
  • .phan
  • .pnpm-patches
  • .vscode
  • docs
  • projects
    Good: Test files detected (projects/github-actions/pr-is-up-to-date/tests).
  • tools
    Good: Environment pinned via tools/docker/Dockerfile.
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .eslintignore.root
  • .gitattributes
  • .gitignore
  • .npmrc
  • .nvmrc
  • .phpcs.config.xml
  • .phpcs.xml.dist
  • .phpcsignore
  • .pnpmfile.cjs
  • .prettierrc.js
  • .shellcheckrc
  • .stylelintignore
  • AGENTS.md
  • CODE-OF-CONDUCT.md
  • composer.json
    Good: Dependency manifest found (composer.json).
  • composer.lock
    Good: Lockfile present (composer.lock). Installs are reproducible.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    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.
    Good: Contributing guide includes code examples.
  • eslint.config.mjs
  • jetpack.php
  • LICENSE.txt
    Good: Licensed under Other.
  • package.json
  • pnpm-lock.yaml
  • pnpm-workspace.yaml
  • 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.
  • SECURITY.md
    Good: Security policy present.
  • stylelint.config.mjs
  • to-test.md
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/automattic/jetpack)](https://www.repo-grade.com/report/automattic/jetpack)

More graded PHP repos