0
/ 100
Polished and well engineered. Punching above its star count.
🏦 Open source, transparency-orientated fiscal sponsorship platform for hackers & creatives.
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.
- 2README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Contributing guide5pt
Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
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
80
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.
README is present.
README documents how to install the project.
Licensed under AGPL-3.0.
Engineering
93
Test files detected (spec).
CI is configured (.github/workflows/ci.yml).
Ruby linting configured (.prettierrc).
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)
- 117Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 860Watchers
Responsiveness
- 11hMedian issue response
- <1hMedian PR merge time
- 357Open issues
Repository files61 root entries
- .devcontainerGood: Environment pinned via .devcontainer/Dockerfile.
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Dependabot covers 3 ecosystems (bundler, npm, github-actions). Dependencies stay current.Good: Issue or PR templates present.
- .vscode
- app
- bin
- config
- db
- dev-docs
- docs
- lib
- log
- public
- runbooks
- scripts
- specGood: Test files detected (spec).
- storage
- vendor
- .annotaterb.yml
- .dockerignore
- .env.development.example
- .erb_lint.yml
- .foreman
- .gitattributes
- .gitignoreGood: .gitignore present.
- .node-version
- .prettierrcGood: Ruby linting configured (.prettierrc).
- .rspec
- .rubocop_todo.yml
- .rubocop.yml
- .ruby-version
- .simplecov
- .slugignore
- .solargraph.yml
- app.json
- Aptfile
- config.ru
- docker_dev_setup.sh
- docker_setup.sh
- docker_start.sh
- docker-compose.dbonly.yml
- docker-compose.production.yml
- docker-compose.solargraph.yml
- docker-compose.yml
- Dockerfile
- eslint.config.mjs
- GemfileGood: Dependency manifest found (Gemfile).
- Gemfile.lockGood: Lockfile present (Gemfile.lock). Installs are reproducible.
- hcb_laser.gif
- heroku.yml
- LICENSEGood: Licensed under AGPL-3.0.
- package.json
- postcss.config.js
- Procfile
- Procfile.dev
- production.Dockerfile
- 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.Good: README documents how to run the project.
- SECURITY.mdGood: Security policy present.
- tailwind.config.js
- webpack.config.js
- yarn.lock
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/hackclub/hcb)