77
/ 100
Solid engineering. The biggest lever is a license.
Classier solution for file uploads for Rails, Sinatra and other Ruby web frameworks
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.
- 3License6pt
Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
- 4Reproducibility6pt
Commit Gemfile.lock so Bundler installs are repeatable.
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
75
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README documents how to install the project.
README is present.
Engineering
70
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/carrierwave/test).
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
- 1 / 6Commits (30d / 90d)
- 1,646Forks
- 39Releaseslatest 6y ago
Community
- 37% - WeakCommunity health
- 3 bus factorauthors own >50% of commits
- 8,782Watchers
Responsiveness
- 1hMedian issue response
- 3d 5hMedian PR merge time
- 66Open issues
Repository files15 root entries
- .githubGood: CI is configured (.github/workflows/test.yml).Good: Dependabot configured for github-actions.
- features
- gemfiles
- libGood: Test files detected (lib/carrierwave/test).
- script
- spec
- .gitignoreGood: .gitignore present.
- .rubocop.ymlGood: Ruby linting configured (.rubocop.yml).
- carrierwave.gemspec
- CHANGELOG.md
- CONTRIBUTING.mdIssue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +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.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.
- cucumber.yml
- GemfileGood: Dependency manifest found (Gemfile).
- 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/carrierwaveuploader/carrierwave)