triton-lang/triton-ascend
Grade a repo

0

/ 100

GradeA

Well engineered for its size. A portfolio piece worth showing off.

Top 12% of 5,156 graded repos

Triton language and compiler for Ascend NPU

Documentation87
Engineering87
Health100
MLIR76MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

9 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

87

README12pt75

README is present.

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt97

Contributing guide is detailed and thorough.

License6pt100

Licensed under MIT.

Engineering

87

Tests18pt80

Test files detected (python/test).

CI/CD14pt85

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

Reproducibility6pt92

Lockfile present (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)
  • 121
    Forks
  • 1
    Releaseslatest 3mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 76
    Watchers

Responsiveness

  • 12d 1h
    Median issue response
  • 22h
    Median PR merge time
  • 216
    Open issues
Repository files41 root entries
  • .github
    Good: CI is configured (.github/workflows/build-docker-image.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • bin
  • cmake
  • docker
    Good: Environment pinned via docker/3.2.1-910b-debian12-py3.11/Dockerfile.
  • docs
  • include
  • 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.
  • .gitmodules
  • .pre-commit-config.yaml
  • .readthedocs.yaml
  • CMakeLists.txt
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING_zh.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    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.
  • GOVERNANCE_zh.md
  • GOVERNANCE.md
  • LICENSE
    Good: Licensed under MIT.
  • MAINTAINERS.md
  • Makefile
  • MANIFEST.in
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • README_zh.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.
    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.
  • README.md
  • RELEASE.md
  • requirements_dev.txt
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
  • safe_compile.cmake
  • SECURITYNOTE_zh.md
  • SECURITYNOTE.md
  • setup.py
  • version.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/triton-lang/triton-ascend)](https://www.repo-grade.com/report/triton-lang/triton-ascend)

More graded MLIR repos