Strong community interest, but tests, CI, or docs need work.
Better error page for Rack apps
Documentation
85
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
55
No RuboCop config found.
→ Add a .rubocop.yml and run `rubocop` in CI to enforce consistent Ruby style.
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 (spec).
CI is configured (.github/workflows/ci.yml).
Project health
79
No pushes in over a year (−80 pts).
→ A recent commit signals the project is alive and worth contributing to.
Dependency manifest found (Gemfile).
Repository has a description.
.gitignore present.
Repository files15 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- feature-screenshots
- gemfiles
- lib
- specGood: Test files detected (spec).
- .coveralls.yml
- .gitignoreGood: .gitignore present.
- .ruby-versionGood: Environment pinned via .ruby-version.
- .yardopts
- better_errors.gemspec
- CHANGELOG.md
- GemfileGood: Dependency manifest found (Gemfile).
- 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.