bazel-contrib/toolchains_llvm

0

/ 100

Documentation82
Engineering56
Health68
Starlark368Apache-2.01d ago
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

LLVM toolchain for bazel

Documentation

82

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

56

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

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

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

Tests18pt80

Test files detected (tests).

Linting and formatting5pt100

Linter or formatter configured (.trunk/configs/.editorconfig).

Project health

68

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

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)
  • 276
    Forks
  • 23
    Releaseslatest 2y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 368
    Watchers

Responsiveness

  • 5h
    Median issue response
  • 5h
    Median PR merge time
  • 73
    Open issues
Repository files19 root entries
  • .bcr
  • .github
    Good: CI is configured (.github/workflows/tests.yml).
  • .trunk
    Good: Linter or formatter configured (.trunk/configs/.editorconfig).
  • docs
  • platforms
  • tests
    Good: Test files detected (tests).
  • toolchain
  • utils
  • .bazelignore
  • .bazelrc
  • .buildifier.json
  • .gitignore
    Good: .gitignore present.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • MODULE.bazel
  • 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.
  • renovate.json
  • REPO_RENAME.md
  • WORKSPACE
  • WORKSPACE.bzlmod