google-ai-edge/litert

0

/ 100

Documentation95
Engineering66
Health100
C++2,583Apache-2.01d ago
Grade a repo

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

LiteRT, successor to TensorFlow Lite. is Google's On-device framework for high-performance ML & GenAI deployment on edge platforms, via efficient conversion, runtime, and optimization

Documentation

95

Contributing guide5pt89

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

66

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

CI/CD14pt57

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

Tests18pt80

Test files detected (ci/tools/python/wheel/utils/manylinux_compliance_test.py).

Reproducibility6pt80

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

Linting and formatting5pt100

Linter or formatter configured (litert/js/packages/core/eslint.config.js).

Project health

100

Dependency manifest6pt100

Dependency manifest found (Package.swift).

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)
  • 350
    Forks
  • 15
    Releaseslatest 6mo ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 2,583
    Watchers

Responsiveness

  • 2d 3h
    Median issue response
  • <1h
    Median PR merge time
  • 2,041
    Open issues
Repository files35 root entries
  • .github
    Good: CI is configured (.github/workflows/clang_tidy.yml).
  • ci
    Good: Test files detected (ci/tools/python/wheel/utils/manylinux_compliance_test.py).
  • cmake_example
  • docker_build
    Good: Lockfile present (docker_build/requirements.txt). Installs are reproducible.
    Good: Environment pinned via docker_build/docker-compose.yml.
  • g3doc
  • litert
    Good: Linter or formatter configured (litert/js/packages/core/eslint.config.js).
  • support
  • tensor
  • tflite
  • third_party
  • weight_loader
  • .bazeliskrc
  • .bazelrc
  • .bazelversion
  • .clang-tidy
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • BUILD
  • BUILD.darts_clone
  • BUILD.sentencepiece
  • BUILD.tomlplusplus
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • configure
  • configure.py
  • 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.
    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).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Package.swift
    Good: Dependency manifest found (Package.swift).
  • PATCH.flatbuffers_windows_no_bash
  • PATCH.protobuf_port_msvc_compat
  • PATCH.sentencepiece
  • 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.
  • WORKSPACE