0
/ 100
Solid foundation. Invest in docs and CI to grow from here.
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 2README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 3Install and run instructions9pt
Add a section showing how to start or use the project.
- 4Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry 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
60
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 MIT.
Engineering
98
Lockfile present (yarn.lock). Installs are reproducible.
Test files detected (packages/client/src/__tests__).
CI is configured (.github/workflows/lint.yml).
Linter or formatter configured (eslint.config.mjs).
Issue or PR templates present.
Project health
67
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
.gitignore present.
Dependency manifest found (package.json).
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 8Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 27Watchers
Responsiveness
- 17d 18hMedian issue response
- 9hMedian PR merge time
- 225Open issues
Repository files30 root entries
- .changeset
- .claude
- .cursor
- .githubGood: CI is configured (.github/workflows/lint.yml).Good: Issue or PR templates present.
- .husky
- .vscode
- .yarn
- docker
- docs
- packagesGood: Test files detected (packages/client/src/__tests__).Good: Environment pinned via packages/email-ingestion-gateway/DockerFile.Issue: Build artifacts or local files may be committed (packages/client/src/components/.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
- scripts
- .env.template
- .gitignoreGood: .gitignore present.
- .node-version
- .nvmrc
- .prettierignore
- .yarnrc.yml
- CLAUDE.md
- codegen.ts
- eslint.config.mjsGood: Linter or formatter configured (eslint.config.mjs).
- graphql.config.js
- LICENSEGood: Licensed under MIT.
- package.jsonGood: Dependency manifest found (package.json).
- prettier.config.mjs
- README.mdGood: 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.
- renovate.json
- todo.md
- tsconfig.json
- vitest.config.ts
- yarn.lockGood: Lockfile present (yarn.lock). Installs are reproducible.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/urigo/accounter-fullstack)