Rough and inactive. Tests, CI, and a fuller README would revive it.
Plugin to show the number of assigned issues with badge on top menu.
Documentation
82
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README documents how to install the project.
README is present.
Licensed under GPL-2.0.
Engineering
57
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.
CI is configured (.github/workflows/greetings.yml).
Test files detected (spec).
Linter or formatter configured (.eslintrc).
Project health
43
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
No pushes in over 2 years. Looks unmaintained (−95 pts).
→ A recent commit signals the project is alive and worth using.
Repository has a description.
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 1Watchers
Responsiveness
- —Median issue response
- —Median PR merge time
- 0Open issues
Repository files23 root entries
- .circleci
- .githubGood: CI is configured (.github/workflows/greetings.yml).
- app
- assets
- config
- db
- lib
- script
- specGood: Test files detected (spec).
- src
- .eslintrcGood: Linter or formatter configured (.eslintrc).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .rubocop_todo.yml
- .rubocop.yml
- docker-compose.yml
- DockerfileGood: Environment pinned via Dockerfile.
- Gemfile.local
- GPL.txt
- init.rb
- LICENSE.txtGood: Licensed under GPL-2.0.
- README_ja.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.
- README.md