84
/ 100
Well engineered. The main gaps are issue and PR templates and a reproducible setup.
An opinionated framework for creating REST-like APIs in Ruby.
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.
- 2Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 3Reproducibility6pt
Commit Gemfile.lock so Bundler installs are repeatable.
- 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
96
README documents how to install the project.
Contributing guide is detailed and thorough.
README is present.
Licensed under MIT.
Engineering
69
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.
No dependency lockfile found (−70 pts).
→ Commit Gemfile.lock so Bundler installs are repeatable.
Test files detected (lib/grape/validations/validations_spec.rb).
CI is configured (.github/workflows/test.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
- 92 / 194Commits (30d / 90d)
- 1,231Forks
- 0Releases
Community
- 62% - FairCommunity health
- 2 bus factorauthors own >50% of commits
- 10,008Watchers
Responsiveness
- 5d 22hMedian issue response
- 5d 6hMedian PR merge time
- 241Open issues
Repository files28 root entries
- .githubGood: CI is configured (.github/workflows/test.yml).
- benchmark
- docker
- gemfiles
- libGood: Test files detected (lib/grape/validations/validations_spec.rb).
- spec
- .coveralls.yml
- .dockerignore
- .gitignoreGood: .gitignore present.
- .rspec
- .rubocop_todo.yml
- .rubocop.ymlGood: Ruby linting configured (.rubocop.yml).
- .simplecov
- .yardopts
- AGENTS.md
- CHANGELOG.md
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.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.
- Dangerfile
- docker-compose.ymlGood: Environment pinned via docker-compose.yml.
- GemfileGood: Dependency manifest found (Gemfile).
- grape.gemspec
- grape.png
- LICENSEGood: Licensed under MIT.
- Rakefile
- 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.
- RELEASING.md
- SECURITY.mdGood: Security policy present.
- UPGRADING.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/ruby-grape/grape)