google-ai-edge/mediapipe

0

/ 100

Documentation82
Engineering63
Health100
C++35,727Apache-2.05d ago
Grade a repo

Popular and well-maintained. A little polish away from elite status.

Cross-platform, customizable ML solutions for live and streaming media.

Documentation

82

Contributing guide5pt61

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.

README12pt75

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

63

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.

CI/CD14pt40

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

Tests18pt80

Test files detected (mediapipe/model_maker/python/core/data/cache_files_test.py).

Reproducibility6pt80

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository files33 root entries
  • .github
    Good: CI is configured (.github/workflows/stale.yaml).
    Good: Issue or PR templates present.
  • docs
  • mediapipe
    Good: Test files detected (mediapipe/model_maker/python/core/data/cache_files_test.py).
  • third_party
  • .bazelrc
  • .bazelversion
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • build_android_examples.sh
  • build_desktop_examples.sh
  • build_ios_examples.sh
  • BUILD.bazel
  • 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.
    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.
    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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Dockerfile.manylinux_2_28_x86_64
  • Dockerfile.manylinux2014_aarch64rp4
  • LICENSE
    Good: Licensed under Apache-2.0.
  • MANIFEST.in
  • MODULE.bazel
  • package.json
    Good: Dependency manifest found (package.json).
  • platform_mappings
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • 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.
    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.
  • requirements_lock_3_10.txt
  • requirements_lock_3_11.txt
  • requirements_lock_3_12.txt
  • requirements_lock.txt
  • requirements.txt
  • setup_android_sdk_and_ndk.sh
  • setup_opencv.sh
  • setup.py
  • tsconfig.json
  • WORKSPACE