Good community traction and solid fundamentals. Nearly in the top tier.
A performance dashboard for Postgres
Documentation
74
README documents how to install the project.
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.
README is present.
Licensed under MIT.
Engineering
66
No RuboCop config found.
→ Add a .rubocop.yml and run `rubocop` in CI to enforce consistent Ruby style.
No dependency lockfile found (−70 pts).
→ Commit Gemfile.lock so Bundler installs are repeatable.
Test files detected (test).
CI is configured (.github/workflows/build.yml).
Issue or PR templates present.
Project health
95
Actively maintained (pushed within 3 months).
Dependency manifest found (Gemfile).
Repository has a description.
.gitignore present.
Repository files17 root entries
- .githubGood: CI is configured (.github/workflows/build.yml).Good: Issue or PR templates present.
- app
- config
- gemfiles
- guides
- lib
- licenses
- testGood: Test files detected (test).
- .gitattributes
- .gitignoreGood: .gitignore present.
- CHANGELOG.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.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.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.
- GemfileGood: Dependency manifest found (Gemfile).
- LICENSE.txtGood: Licensed under MIT.
- pghero.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.