70
/ 100
Good shape overall. A few tweaks would push it into the top tier.
The flagship TRMNL BYOS application.
Top 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
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues 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
62
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
63
No RuboCop config found.
→ Add a .rubocop.yml and run `rubocop` in CI to enforce consistent Ruby style.
CI is configured (.github/workflows/docker.yml).
Test files detected (spec).
Lockfile present (Gemfile.lock). Installs are reproducible.
Issue or PR templates present.
Project health
100
Dependency manifest found (Gemfile).
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)
- 114Forks
- 0Releases
Community
- 75% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 612Watchers
Responsiveness
- 5hMedian issue response
- <1hMedian PR merge time
- 1Open issues
Repository files30 root entries
- .circleci
- .config
- .githubGood: CI is configured (.github/workflows/docker.yml).Good: Issue or PR templates present.
- app
- bin
- config
- doc
- lib
- public
- scripts
- slices
- specGood: Test files detected (spec).
- .dockerignore
- .gitignoreGood: .gitignore present.
- .hadolint.yml
- .node-version
- .reek.yml
- .ruby-version
- compose.yml
- config.ru
- DockerfileGood: Environment pinned via Dockerfile.
- GemfileGood: Dependency manifest found (Gemfile).
- Gemfile.lockGood: Lockfile present (Gemfile.lock). Installs are reproducible.
- LICENSE.adocGood: Licensed under MIT.
- package-lock.json
- package.json
- Procfile
- Rakefile
- README.adocGood: README is present.Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.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.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.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.Good: README documents how to run the project.
- render.yaml
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/usetrmnl/terminus)