94
/ 100
Excellent work. The main thing left to polish is the repo description and topics. It just hasn't found an audience yet.
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a lint step to catch style issues automatically.
- 2CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 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
98
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
93
Lockfile present (package-lock.json). Installs are reproducible.
CI is configured (.github/workflows/test.yml).
Test files detected (__tests__).
Linter or formatter configured (eslint.config.mjs).
Issue or PR templates present.
Project health
68
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.
Dependency manifest found (package.json).
Actively maintained (pushed within 3 months).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 0 / 417Commits (30d / 90d)
- 1Forks
- 0Releases
Community
- 85% - GoodCommunity health
- 4 bus factorauthors own >50% of commits
- 5Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 277Open issues
Repository files32 root entries
- __tests__Good: Test files detected (__tests__).
- .githubGood: CI is configured (.github/workflows/test.yml).Good: Issue or PR templates present.
- .vscode
- arena-socket-server
- backend
- docs
- public
- security-tests
- src
- styles
- .env.example
- .gitignoreGood: .gitignore present.
- Architecture.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- design.md
- DockerfileGood: Environment pinned via Dockerfile.
- eslint.config.mjsGood: Linter or formatter configured (eslint.config.mjs).
- jest.config.js
- jest.setup.js
- jsconfig.json
- LICENSEGood: Licensed under MIT.
- next-sitemap.config.js
- next.config.mjs
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- postcss.config.js
- 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.
- render.yaml
- SECURITY.mdGood: Security policy present.
- supabase_setup.sql
- tailwind.config.js
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/pankajsingh34/algobuddy)