64
/ 100
A workable base with real gaps. Start with CI and issue and PR templates.
π π½ππππππππΏ@ πΌπ πππππππππππ ππππΎππΌπ πΏπ πππ½π πππππππ π½ππ, ππ π½ππ πΏπ ππππππππππΏπππππππ, π πππππ πππ, ππππππΜπ πΏπ ππππππ π πππΎππ ππΌπ. ππ ππ πππππΌ ππππ ππππππΎππ, πΌππππΌπππ πΎππ πππΌ ππππππππΌ π
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to A (92).
See your top fixesTop 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.
- 2CI/CD14pt
If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
- 3Reproducibility6pt
Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
- 4Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry, or a renovate.json, so dependencies are updated automatically.
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
84
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 is present.
README documents how to install the project.
Licensed under MIT.
Engineering
48
No CI configuration detected in this repository.
β If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
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.
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
A test script is configured in package.json.
Linter or formatter configured (lint script in package.json).
Project health
94
Dependency manifest found (package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 47Forks
- 0Releases
Community
- 42% - WeakCommunity health
- -authors own >50% of commits
- 94Watchers
Responsiveness
- -Median issue response
- <1hMedian PR merge time
- 11Open issues
Repository files13 root entries
- scripts
- src
- tmp
- .env.example
- .gitignoreGood: .gitignore present.
- index.js
- LICENSE.txtGood: Licensed under MIT.
- logo.ico
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- 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.
- settings.js
- termux-install.sh
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/dioneibi-rip/ruby-hoshino-bot)