taichi-dev/taichi
Grade a repo

86

/ 100

GradeB

A top-tier open source project. Docs, tests, and CI are all in excellent shape.

Top 20% of 5,156 graded repos

Productive, portable, and performant GPU programming in Python.

Documentation93
Engineering77
Health100
C++28,288Apache-2.01mo 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 step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

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

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

93

Contributing guide5pt70

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.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

77

CI/CD14pt57

CI is configured (.github/workflows/build.yaml).

Reproducibility6pt70

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

Tests18pt80

Test files detected (c_api/tests).

Linting and formatting5pt100

Linter or formatter configured (.pylintrc).

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

  • 0 / 0
    Commits (30d / 90d)
  • 2,385
    Forks
  • 118
    Releaseslatest 6y ago

Community

  • 75% - Good
    Community health
  • 3 bus factor
    authors own >50% of commits
  • 28,288
    Watchers

Responsiveness

  • 7h
    Median issue response
  • <1h
    Median PR merge time
  • 923
    Open issues
Repository files36 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yaml).
    Good: Issue or PR templates present.
  • benchmarks
    Good: Lockfile present (benchmarks/requirements.txt). Installs are reproducible.
  • c_api
    Good: Test files detected (c_api/tests).
  • ci
  • cmake
  • conda
  • cpp_examples
  • docs
  • external
  • misc
  • python
  • scripts
  • taichi
  • tests
  • .clang-format
  • .clang-tidy
  • .git-blame-ignore-revs
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .pre-commit-config.yaml
  • .pylintrc
    Good: Linter or formatter configured (.pylintrc).
  • build.py
  • 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.
    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.
    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.
  • MANIFEST.in
  • netlify.toml
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • 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.
  • requirements_dev.txt
  • requirements_test.txt
  • setup.cfg
  • setup.py
  • version.txt
  • vs-chromium-project.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/taichi-dev/taichi)](https://www.repo-grade.com/report/taichi-dev/taichi)

More graded C++ repos