microsoft/onnxruntime

0

/ 100

Documentation71
Engineering80
Health88
C++20,908MITtoday
Grade a repo

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

ONNX Runtime: cross-platform, high performance ML inferencing and training accelerator

Documentation

71

Install and run instructions9pt45

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

→ Add a section showing how to install dependencies.

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt75

README is present.

License6pt100

Licensed under MIT.

Engineering

80

CI/CD14pt57

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

Tests18pt80

Test files detected (csharp/test).

Linting and formatting5pt100

Linter or formatter configured (js/.prettierrc).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

88

Dependency manifest6pt62

Dependency manifest found (pyproject.toml).

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

  • 209 / 914
    Commits (30d / 90d)
  • 4,013
    Forks
  • 72
    Releaseslatest 6y ago

Community

  • 100% - Good
    Community health
  • 19 bus factor
    authors own >50% of commits
  • 20,908
    Watchers

Responsiveness

  • 11h
    Median issue response
  • 23h
    Median PR merge time
  • 1,369
    Open issues
Repository files58 root entries
  • .agents
  • .config
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/lint.yml).
    Good: Dependabot covers 2 ecosystems (pip, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • .vscode
  • cgmanifests
  • cmake
  • csharp
    Good: Test files detected (csharp/test).
  • dockerfiles
  • docs
  • include
  • java
  • js
    Good: Linter or formatter configured (js/.prettierrc).
  • model_package
  • objectivec
  • onnxruntime
  • orttraining
  • plugin-ep-cuda
  • plugin-ep-webgpu
  • rust
  • samples
  • tools
  • winml
  • .clang-format
  • .clang-tidy
  • .dockerignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .ignore
  • .lintrunner.toml
  • AGENTS.md
  • build_arm64x.bat
  • build.bat
  • build.sh
  • CITATION.cff
  • 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.
    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.
  • CPPLINT.cfg
  • lgtm.yml
  • LICENSE
    Good: Licensed under MIT.
  • NuGet.config
  • ORT_icon_for_light_bg.png
  • ort.wprp
  • packages.config
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • 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.
    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.
  • requirements-dev.txt
  • requirements-doc.txt
  • requirements-lintrunner.txt
  • requirements-training.txt
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
  • SECURITY.md
    Good: Security policy present.
  • setup.py
  • SUPPORT.md
  • ThirdPartyNotices.txt
  • VERSION_NUMBER