tenstorrent/tt-mlir

0

/ 100

Documentation85
Engineering63
Health100
MLIR281Apache-2.01d ago
Grade a repo

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

Tenstorrent MLIR compiler

Documentation

85

Contributing guide5pt58

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

63

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

CI is configured (.github/workflows/call-build-debug.yml).

Tests18pt80

Test files detected (.github/scripts/python/test_common.py).

Reproducibility6pt80

Lockfile present (test/python/requirements.txt). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (python/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)
  • 132
    Forks
  • 232
    Releaseslatest 12mo ago

Community

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

Responsiveness

  • 8d 7h
    Median issue response
  • 10h
    Median PR merge time
  • 1,279
    Open issues
Repository files26 root entries
  • .claude
  • .github
    Good: Test files detected (.github/scripts/python/test_common.py).
    Good: CI is configured (.github/workflows/call-build-debug.yml).
    Good: Issue or PR templates present.
  • .test_durations
  • cmake
  • docs
  • env
  • include
  • lib
  • python
    Good: Dependency manifest found (python/pyproject.toml).
  • runtime
  • test
    Good: Lockfile present (test/python/requirements.txt). Installs are reproducible.
  • third_party
  • tools
    Good: Environment pinned via tools/explorer/hosted/docker-compose.yml.
  • .clang-format
  • .clang-format-ignore
  • .clang-tidy
  • .gitignore
    Good: .gitignore present.
  • .pre-commit-config.yaml
  • AGENTS.md
  • CLAUDE.md
  • CMakeLists.txt
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +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.
  • LICENSE_understanding.txt
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.