Good shape overall. A few tweaks would push it into the top tier.

Exercism exercises in Ruby.

Documentation

62

Contributing guide5pt30

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.

Install and run instructions9pt45

README documents how to install the project.

README12pt70

README is present.

License6pt100

Licensed under MIT.

Engineering

79

Issue and PR templates6pt0

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.

Tests18pt80

Test files detected (exercises/concept/amusement-park-improvements/attendee_test.rb).

Reproducibility6pt92

Lockfile present (Gemfile.lock). Installs are reproducible.

CI/CD14pt100

CI is configured (.github/workflows/exercise-tests.yml).

Linting and formatting5pt100

Ruby linting configured (.rubocop.yml).

Project health

100

Dependency manifest6pt100

Dependency manifest found (Gemfile).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 530
    Forks
  • 0
    Releases

Community

  • Community health
  • authors own >50% of commits
  • 597
    Watchers

Responsiveness

  • 8h
    Median issue response
  • 3h
    Median PR merge time
  • 12
    Open issues
Repository files23 root entries
  • .appends
  • .github
    Good: CI is configured (.github/workflows/exercise-tests.yml).
    Good: Dependabot configured for github-actions.
  • bin
  • concepts
  • docs
  • exercises
    Good: Test files detected (exercises/concept/amusement-park-improvements/attendee_test.rb).
  • generatorv2
  • lib
  • reference
  • test
  • .gitignore
    Good: .gitignore present.
  • .rubocop.yml
    Good: Ruby linting configured (.rubocop.yml).
  • .ruby-version
    Good: Environment pinned via .ruby-version.
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • config.json
  • exercise-concepts.todo.json
  • Gemfile
    Good: Dependency manifest found (Gemfile).
  • Gemfile.lock
    Good: Lockfile present (Gemfile.lock). Installs are reproducible.
  • LICENSE
    Good: Licensed under MIT.
  • package.json
  • Rakefile
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    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.
  • yarn.lock