arm/arm-toolchain

0

/ 100

Documentation64
Engineering72
Health100
LLVM226Other1d ago
Grade a repo

Good shape overall. A few tweaks would push it into the top tier.

A project dedicated to building LLVM toolchain for Arm and AArch64 embedded targets and AArch64 native Linux development.

Documentation

64

README12pt18

This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.

Contributing guide5pt85

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

72

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

CI/CD14pt72

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

Tests18pt80

Test files detected (.ci/compute_projects_test.py).

Reproducibility6pt80

Lockfile present (.ci/metrics/requirements.txt). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (.ci/metrics/requirements.txt).

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)
  • 49
    Forks
  • 6
    Releaseslatest 3mo ago

Community

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

Responsiveness

  • 12h
    Median issue response
  • <1h
    Median PR merge time
  • 27
    Open issues
Repository files24 root entries
  • .ci
    Good: Test files detected (.ci/compute_projects_test.py).
    Good: Lockfile present (.ci/metrics/requirements.txt). Installs are reproducible.
    Good: Environment pinned via .ci/metrics/Dockerfile.
    Good: Dependency manifest found (.ci/metrics/requirements.txt).
  • .github
    Good: CI is configured (.github/workflows/check_downstream_changes.yml).
    Good: Issue or PR templates present.
  • arm-software
  • bolt
  • clang
  • clang-tools-extra
  • cmake
  • compiler-rt
  • cross-project-tests
  • flang
  • flang-rt
  • libc
  • .clang-format
  • .clang-format-ignore
  • .clang-tidy
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mailmap
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • LICENSE.TXT
    Good: Licensed under Other.
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    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.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.
    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.