0
/ 100
Good community traction and solid fundamentals. Nearly in the top tier.
A high-performance inference engine for AI models
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 2CI/CD14pt
Add a lint step to catch style issues automatically.
- 3CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
84
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
73
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 is configured (.github/workflows/tests.yml).
Lockfile present (Cargo.lock). Installs are reproducible.
Test files detected (bindings/python/tests).
Rust linting configured (bindings/typescript/.prettierrc.json).
Project health
100
Dependency manifest found (Cargo.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 59Forks
- 11Releaseslatest 2mo ago
Community
- -Community health
- -authors own >50% of commits
- 1,635Watchers
Responsiveness
- 6hMedian issue response
- <1hMedian PR merge time
- 11Open issues
Repository files31 root entries
- .cargo
- .config
- .githubGood: CI is configured (.github/workflows/tests.yml).
- .helix
- .vscode
- .zed
- apps
- bindingsGood: Test files detected (bindings/python/tests).Good: Rust linting configured (bindings/typescript/.prettierrc.json).
- crates
- scripts
- toolsGood: Environment pinned via tools/.python-version.
- workspace
- .clang-format
- .env.sample
- .envrc
- .gitignoreGood: .gitignore present.
- .swift-format
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- clippy.toml
- CODEOWNERS
- deny.toml
- flake.lock
- flake.nix
- LICENSEGood: Licensed under MIT.
- Package.swift
- platforms.toml
- README.mdGood: 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.
- rust-analyzer.toml
- rust-toolchain.toml
- rustfmt.toml
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/trymirai/uzu)