intel/intel-xpu-backend-for-triton
Grade a repo

90

/ 100

GradeA

Polished and well engineered. Punching above its star count.

Top 12% of 5,156 graded repos

OpenAI Triton backend for Intel® GPUs

Documentation91
Engineering86
Health100
MLIR257MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

91

Contributing guide5pt59

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

86

Tests18pt80

Test files detected (benchmarks/tests).

Reproducibility6pt82

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

CI/CD14pt85

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

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

  • 298 / 1086
    Commits (30d / 90d)
  • 103
    Forks
  • 18
    Releaseslatest 1y ago

Community

  • 100% - Good
    Community health
  • 6 bus factor
    authors own >50% of commits
  • 257
    Watchers

Responsiveness

  • 17d 1h
    Median issue response
  • 23h
    Median PR merge time
  • 306
    Open issues
Repository files36 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/build-benchmarks-wheel.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • benchmarks
    Good: Test files detected (benchmarks/tests).
  • bin
  • cmake
  • docs
    Good: Lockfile present (docs/requirements.txt). Installs are reproducible.
  • examples
  • include
  • lib
  • python
  • scripts
  • test
  • third_party
  • unittest
  • utils
  • .clang-format
  • .claudeignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .git-blame-ignore-revs
  • .gitignore
    Good: .gitignore present.
  • .pre-commit-config.yaml
  • AGENTS.md
  • bandit.yaml
  • 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.
  • DEVELOPMENT.md
  • LICENSE
    Good: Licensed under MIT.
  • Makefile
  • MANIFEST.in
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • pytest.ini
  • 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.
  • RELEASE.md
  • SECURITY.md
    Good: Security policy present.
  • setup.py
  • third-party-programs.txt
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/intel/intel-xpu-backend-for-triton)](https://www.repo-grade.com/report/intel/intel-xpu-backend-for-triton)

More graded MLIR repos