76
/ 100
Good shape overall. A few tweaks would push it into the top tier.
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.
- 2Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
- 3Issue and PR templates6pt
Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
- 4Issue and PR templates6pt
A SECURITY.md explains how to responsibly disclose vulnerabilities. Worth adding once the project has real users.
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
68
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
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.
Test files detected (days/day-16/solutions/blog-api/test).
Lockfile present (days/day-11/solutions/todo-api-ts/pnpm-lock.yaml). Installs are reproducible.
CI is configured (solutions/blog/.github/workflows/ci.yml).
Project health
84
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 (days/day-10/solutions/mini-todo-api/package.json).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 56Forks
- 0Releases
Community
- 28% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 398Watchers
Responsiveness
- 24hMedian issue response
- <1hMedian PR merge time
- 1Open issues
Repository files8 root entries
- cheatsheets
- daysGood: Test files detected (days/day-16/solutions/blog-api/test).Good: Lockfile present (days/day-11/solutions/todo-api-ts/pnpm-lock.yaml). Installs are reproducible.Good: Environment pinned via days/day-21/solutions/blog-db/docker-compose.yml.Good: Dependency manifest found (days/day-10/solutions/mini-todo-api/package.json).
- resources
- solutionsGood: CI is configured (solutions/blog/.github/workflows/ci.yml).
- .gitignoreGood: .gitignore present.
- LICENSEGood: Licensed under MIT.
- 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.
- ROADMAP.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/crisweb1994/60-days-nodejs)