0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Agentic Development Environment for Devs Who Don't Ship Slop
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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
88
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.
A license file is present.
Engineering
68
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/mobile-testflight.yml).
Lockfile present (projects/electron/package-lock.json). Installs are reproducible.
Test files detected (projects/electron/src/modules/code/binaries.test.ts).
Linter or formatter configured (projects/harness/biome.json).
Project health
100
Dependency manifest found (projects/electron/package.json).
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)
- 21Forks
- 29Releaseslatest 4mo ago
Community
- -Community health
- -authors own >50% of commits
- 320Watchers
Responsiveness
- 71d 22hMedian issue response
- 1d 8hMedian PR merge time
- 4Open issues
Repository files10 root entries
- .claude
- .githubGood: CI is configured (.github/workflows/mobile-testflight.yml).
- projectsGood: A license file is present.Good: Test files detected (projects/electron/src/modules/code/binaries.test.ts).Good: Linter or formatter configured (projects/harness/biome.json).Good: Lockfile present (projects/electron/package-lock.json). Installs are reproducible.Good: Dependency manifest found (projects/electron/package.json).
- .gitignoreGood: .gitignore present.
- agents.md
- CLAUDE.md
- logo.png
- openade.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.
- venvy.toml
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/bearlyai/openade)