google/xnnpack

0

/ 100

Documentation60
Engineering46
Health68
C2,365Other1d ago
Grade a repo

Strong community interest, but tests, CI, or docs need work.

High-efficiency floating-point neural network inference operators for mobile, server, and Web

Documentation

60

Install and run instructions9pt45

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

→ Add a section showing how to install dependencies.

Contributing guide5pt53

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.

README12pt55

README is present.

License6pt100

Licensed under Other.

Engineering

46

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.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

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/build-linux-windows.yml).

Tests18pt80

Test files detected (test).

Project health

68

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

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)
  • 509
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 7h
    Median issue response
  • <1h
    Median PR merge time
  • 333
    Open issues
Repository files37 root entries
  • .github
    Good: CI is configured (.github/workflows/build-linux-windows.yml).
  • bench
  • build_config
  • build_overrides
  • cmake
  • doc
  • docker
  • gemm_compiler
  • gen
  • include
  • litert
  • scripts
  • src
  • test
    Good: Test files detected (test).
  • third_party
  • tools
  • ynnpack
  • .bazelrc
  • .clang-format
  • .gitignore
    Good: .gitignore present.
  • .gn
  • build_defs.bzl
  • build_params.bzl
  • build_srcs.bzl
  • BUILD.bazel
  • BUILD.gn
  • BUILD.md
  • CMakeLists.txt
  • 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).
    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.
  • DEPS
  • emscripten.bzl
  • generated_file.bzl
  • LICENSE
    Good: Licensed under Other.
  • MODULE.bazel
  • preamble.js.lds
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    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.
    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.
  • register_extension_info.bzl