0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Ruby AI Framework
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.
- 2README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
- 3Install and run instructions9pt
Add a section showing how to start or use the project.
- 4Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
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
78
README documents how to install the project.
README is present.
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.
Licensed under MIT.
Engineering
79
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.
Test files detected (spec).
Lockfile present (Gemfile.lock). Installs are reproducible.
CI is configured (.github/workflows/build-deploy-docs.yml).
Ruby linting configured (.rubocop.yml).
Project health
100
Dependency manifest found (Gemfile).
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)
- 12Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 297Watchers
Responsiveness
- 5hMedian issue response
- <1hMedian PR merge time
- 0Open issues
Repository files31 root entries
- .claude
- .cursor
- .githubGood: CI is configured (.github/workflows/build-deploy-docs.yml).Good: Dependabot covers 4 ecosystems (bundler, bundler, npm, github-actions). Dependencies stay current.
- app
- bin
- config
- db
- docs
- exe
- gemfiles
- lib
- script
- specGood: Test files detected (spec).
- vcr_cassettes
- .annotaterb.yml
- .erb_lint.yml
- .gitignoreGood: .gitignore present.
- .rspec
- .rubocop.ymlGood: Ruby linting configured (.rubocop.yml).
- CHANGELOG.md
- CLAUDE.md
- CONTRIBUTING.mdIssue: 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.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- GemfileGood: Dependency manifest found (Gemfile).
- Gemfile.lockGood: Lockfile present (Gemfile.lock). Installs are reproducible.
- Guardfile
- MIT-LICENSE
- package.json
- raif.gemspec
- Rakefile
- README.mdGood: 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.Good: README includes status badges.Good: README documents how to install the project.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- yarn.lock
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/cultivatelabs/raif)