facebookexperimental/triton

0

/ 100

Documentation80
Engineering82
Health100
MLIR173MIT1d ago
Grade a repo

Polished and well engineered. Punching above its star count.

Github mirror of trition-lang/triton repo.

Documentation

80

Contributing guide5pt59

Contributing guide is detailed and thorough.

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

82

CI/CD14pt72

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

Tests18pt80

Test files detected (python/test).

Reproducibility6pt82

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

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

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)
  • 55
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 1d 23h
    Median issue response
  • 2d
    Median PR merge time
  • 150
    Open issues
Repository files33 root entries
  • .ci
  • .claude
  • .github
    Good: CI is configured (.github/workflows/build-macos.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • .llms
  • bin
  • bitequiv
  • cmake
  • docs
    Good: Lockfile present (docs/requirements.txt). Installs are reproducible.
  • examples
  • include
  • infra
  • lib
  • python
    Good: Test files detected (python/test).
  • scripts
  • test
  • third_party
  • unittest
  • utils
  • .clang-format
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .git-blame-ignore-revs
  • .gitignore
    Good: .gitignore present.
  • .pre-commit-config.yaml
  • CLAUDE.md
  • CMakeLists.txt
  • 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.
    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 MIT.
  • Makefile
  • MANIFEST.in
  • 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.
  • RELEASE.md
  • setup.py