83

/ 100

GradeB

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

Top 22% of 5,156 graded repos

Carbon Language's main repository: documents, design, implementation, and related tools. (NOTE: Carbon Language is experimental; see README)

Top fixes

Highest-impact changes first, ranked by point weight

13 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 a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

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

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 guide5pt93

Contributing guide is detailed and thorough.

License6pt100

Licensed under Other.

Engineering

78

CI/CD14pt57

CI is configured (.github/workflows/check_dependent_pr.yaml).

Tests18pt80

Test files detected (bazel/cc_toolchains/cc_tools_test.py).

Reproducibility6pt80

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

Linting and formatting5pt100

Linter or formatter configured (.prettierrc.yaml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

91

Dependency manifest6pt71

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

  • -
    Commits (30d / 90d)
  • 1,535
    Forks
  • 709
    Releaseslatest 2y ago

Community

  • 100% - Good
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 33,852
    Watchers

Responsiveness

  • 10d 22h
    Median issue response
  • 2d 2h
    Median PR merge time
  • 236
    Open issues
Repository files42 root entries
  • .agents
  • .github
    Good: CI is configured (.github/workflows/check_dependent_pr.yaml).
    Good: Issue or PR templates present.
  • .vscode
  • bazel
    Good: Test files detected (bazel/cc_toolchains/cc_tools_test.py).
  • common
  • core
  • docs
  • examples
  • github_tools
    Good: Lockfile present (github_tools/requirements.txt). Installs are reproducible.
  • proposals
  • scripts
  • testing
  • third_party
  • toolchain
  • utils
  • website
  • .bazelignore
  • .bazelrc
  • .bazelversion
  • .clang-format
  • .clang-tidy
  • .clangd
  • .codespell_ignore
  • .gdbinit
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .lldbinit
  • .pre-commit-config.yaml
  • .prettierrc.yaml
    Good: Linter or formatter configured (.prettierrc.yaml).
  • .python-version
    Good: Environment pinned via .python-version.
  • AGENTS.md
  • BUILD
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CODEOWNERS
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • LICENSE
    Good: Licensed under Other.
  • MODULE.bazel
  • MODULE.bazel.lock
  • 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.
    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.
  • version_base.bzl
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/carbon-language/carbon-lang)](https://www.repo-grade.com/report/carbon-language/carbon-lang)

More graded C++ repos