92
/ 100
Well engineered for its size. A portfolio piece worth showing off.
Read replica proxy adapters for ActiveRecord!
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
Add additional package-ecosystem entries (especially github-actions) to keep all dependencies current.
- 4Reproducibility6pt
Use a multi-stage Dockerfile.
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
86
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 documents how to install the project.
README is present.
Licensed under MIT.
Engineering
92
Test files detected (spec).
Lockfile present (Gemfile.lock). Installs are reproducible.
CI is configured (.github/workflows/test.yml).
Ruby linting configured (.rubocop.yml).
Issue or PR templates present.
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
- 10 / 40Commits (30d / 90d)
- 11Forks
- 53Releaseslatest 1y ago
Community
- 75% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 83Watchers
Responsiveness
- 6hMedian issue response
- 5hMedian PR merge time
- 0Open issues
Repository files24 root entries
- .githubGood: CI is configured (.github/workflows/test.yml).Good: Dependabot configured for bundler.Good: Issue or PR templates present.
- bin
- db
- docker
- gemfiles
- lib
- sig
- specGood: Test files detected (spec).
- .app-image-tag
- .dockerignore
- .gitignoreGood: .gitignore present.
- .rspec
- .rubocop.ymlGood: Ruby linting configured (.rubocop.yml).
- active_record_proxy_adapters.gemspec
- Appraisals
- CHANGELOG.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- docker-compose.yml
- DockerfileGood: Environment pinned via Dockerfile.
- GemfileGood: Dependency manifest found (Gemfile).
- Gemfile.lockGood: Lockfile present (Gemfile.lock). Installs are reproducible.
- LICENSE.txtGood: 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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/nasdaq/active_record_proxy_adapters)