85
/ 100
Well engineered. The main gaps are issue and PR templates and a contributing guide.
Plan, Build, and Ship — with a team of AI agents instead of one
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a lint step to catch style issues automatically.
- 2CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 4Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry, or a renovate.json, so dependencies are updated automatically.
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
89
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README is present.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
81
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.
Lockfile present (Cargo.lock). Installs are reproducible.
CI is configured (.github/workflows/test.yml).
Test files detected (assets/skills/pdf/scripts/check_bounding_boxes_test.py).
Linter or formatter configured (rustfmt.toml).
Project health
79
Dependency manifest found (Cargo.toml).
.gitignore present.
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 34 / 593Commits (30d / 90d)
- 77Forks
- 66Releaseslatest 6mo ago
Community
- 50% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 612Watchers
Responsiveness
- 8hMedian issue response
- <1hMedian PR merge time
- 18Open issues
Repository files31 root entries
- .cargo
- .githubGood: CI is configured (.github/workflows/test.yml).
- .qwen
- assetsGood: Test files detected (assets/skills/pdf/scripts/check_bounding_boxes_test.py).
- binary
- crates
- docs
- frontend
- npxIssue: Build artifacts or local files may be committed (npx/openteams-npx/node_modules/.package-lock.json) (−40 pts).Fix: Remove them and add to .gitignore.
- openteams-cliGood: Environment pinned via openteams-cli/packages/openteams-cli/Dockerfile.
- readmesGood: 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.
- scripts
- shared
- src-tauri
- .dockerignore
- .gitignoreGood: .gitignore present.
- .npmrc
- AGENTS.md
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CLAUDE.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- LICENSEGood: Licensed under Apache-2.0.
- local-build.sh
- package-lock.json
- package.json
- pnpm-lock.yaml
- pnpm-workspace.yaml
- README.md
- rust-toolchain.toml
- rustfmt.tomlGood: Linter or formatter configured (rustfmt.toml).
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/openteams-lab/openteams)