google-ai-edge/litert-torch
Grade a repo

84

/ 100

GradeB

Good community traction and solid fundamentals. Nearly in the top tier.

Top 24% of 5,156 graded repos

Support PyTorch model conversion with LiteRT.

Documentation95
Engineering70
Health100
Jupyter Notebook1,047Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

12 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 `pull_request:` to the workflow `on:` triggers.

  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

95

Contributing guide5pt86

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

70

Linting and formatting5pt0

No Java/Kotlin linter configured.

→ Add Checkstyle or Spotless for Java formatting, or ktlint/Detekt for Kotlin. Run it via Maven/Gradle or as a CI step.

CI/CD14pt68

CI is configured (.github/workflows/nightly_unittests.yml).

Reproducibility6pt70

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

Tests18pt80

Test files detected (litert_torch/_convert/fx_passes/test).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (requirements.txt).

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

  • 17 / 30
    Commits (30d / 90d)
  • 168
    Forks
  • 9
    Releaseslatest 2mo ago

Community

  • 50% - Fair
    Community health
  • 4 bus factor
    authors own >50% of commits
  • 1,047
    Watchers

Responsiveness

  • 1d 9h
    Median issue response
  • 3h
    Median PR merge time
  • 172
    Open issues
Repository files22 root entries
  • .github
    Good: CI is configured (.github/workflows/nightly_unittests.yml).
    Good: Issue or PR templates present.
  • bazel
  • build_config
  • ci
  • docs
  • litert_torch
    Good: Test files detected (litert_torch/_convert/fx_passes/test).
  • test
  • .bazelrc
  • .bazelversion
  • .gitignore
    Good: .gitignore present.
  • .isort.cfg
  • 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.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • dev-requirements.txt
  • format.sh
  • LICENSE
    Good: Licensed under Apache-2.0.
  • MODULE.bazel
  • 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.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (requirements.txt).
  • run_tests.sh
  • setup.py
  • SKILL.md
  • WORKSPACE
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/google-ai-edge/litert-torch)](https://www.repo-grade.com/report/google-ai-edge/litert-torch)

More graded Jupyter Notebook repos