Popular and well-maintained. A little polish away from elite status.

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

Documentation

85

README12pt70

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 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.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    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