0

/ 100

GradeD

Rough and inactive. Tests, CI, and a fuller README would revive it.

Higher than 49% of 5,156 graded repos

TensorFlow Lite for Microcontrollers

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to C (77).

See your top fixes
Now
D
65
Potential
C
77

Top fixes

Highest-impact changes first, ranked by point weight

17 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

76

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

Add a section showing how to install dependencies.

Contributing guide5pt80

Contributing guide is detailed and thorough.

README12pt85

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

54

Linting and formatting5pt0

No linter or formatter config found.

Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

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/check_pr_has_bug.yml).

Reproducibility6pt70

Lockfile present (tensorflow/lite/micro/examples/magic_wand/train/requirements.txt). Installs are reproducible.

Tests18pt80

Test files detected (tensorflow/lite/micro/examples/magic_wand/train/data_augmentation_test.py).

Project health

75

Activity5pt5

No pushes in over 2 years. Looks unmaintained (−95 pts).

A recent commit signals the project is alive and worth using.

Dependency manifest6pt100

Dependency manifest found (tensorflow/lite/micro/examples/magic_wand/train/requirements.txt).

Repository metadata5pt100

Repository has a description.

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 0
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • -
    Median issue response
  • -
    Median PR merge time
  • 0
    Open issues
Repository files15 root entries
  • .github
    Good: CI is configured (.github/workflows/check_pr_has_bug.yml).
  • ci
  • data
  • docs
  • tensorflow
    Good: Test files detected (tensorflow/lite/micro/examples/magic_wand/train/data_augmentation_test.py).
    Good: Lockfile present (tensorflow/lite/micro/examples/magic_wand/train/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (tensorflow/lite/micro/examples/magic_wand/train/requirements.txt).
  • third_party
  • .bazelrc
  • .clang-format
  • .gitignore
    Good: .gitignore present.
  • AUTHORS
  • CODEOWNERS
  • 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.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • README.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.
    Good: README includes status badges.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • 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/huxioan/tflite-micro)](https://www.repo-grade.com/report/huxioan/tflite-micro)

More graded C++ repos