google/jax
Grade a repo

91

/ 100

GradeA

A top-tier open source project. Docs, tests, and CI are all in excellent shape.

Top 11% of 5,156 graded repos

Composable transformations of Python+NumPy programs: differentiate, vectorize, JIT to GPU/TPU, and more

Documentation89
Engineering94
Health88
Python35,917Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

17 to address
  1. 1
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  2. 2
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  3. 3
    CI/CD14pt

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

  4. 4
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

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

89

Contributing guide5pt47

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.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

94

CI/CD14pt85

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

Reproducibility6pt90

Lockfile present (docs/requirements.txt). Installs are reproducible.

Tests18pt100

Test files detected (conftest.py).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

88

Dependency manifest6pt62

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

  • 549 / 1979
    Commits (30d / 90d)
  • 3,662
    Forks
  • 138
    Releaseslatest 4y ago

Community

  • 62% - Fair
    Community health
  • 5 bus factor
    authors own >50% of commits
  • 35,917
    Watchers

Responsiveness

  • 9h
    Median issue response
  • <1h
    Median PR merge time
  • 2,470
    Open issues
Repository files35 root entries
  • .github
    Good: CI is configured (.github/workflows/build_artifacts.yml).
    Good: Dependabot covers 2 ecosystems (pip, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • benchmarks
  • build
  • ci
  • cloud_tpu_colabs
  • docs
    Good: Lockfile present (docs/requirements.txt). Installs are reproducible.
  • examples
  • images
  • jax
  • jax_plugins
  • jaxlib
  • tests
  • third_party
  • .bazelrc
  • .bazelversion
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • .pre-commit-config.yaml
  • .readthedocs.yml
  • AUTHORS
  • bazel_downloader.cfg
  • build_wheel.py
  • BUILD.bazel
  • CHANGELOG.md
  • CITATION.bib
  • conftest.py
    Good: Test files detected (conftest.py).
  • 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.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • MODULE.bazel
  • platform_mappings
  • 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.
  • setup.py
  • test_shard_count.bzl
  • WORKSPACE
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/google/jax)](https://www.repo-grade.com/report/google/jax)

More graded Python repos