0
/ 100
A well-known project done right. Strong docs and solid engineering throughout.
The fast all-in-one Node.js toolkit
Top fixes
Highest-impact changes first, ranked by point weight
- 1Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 2Reproducibility6pt
Ensure .github/dependabot.yml lists 2+ package-ecosystem entries (e.g. your language plus github-actions).
- 3Issue and PR templates6pt
Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
- 4Dependency manifest6pt
Add a `keywords` array to help people find your package on npm.
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
93
CONTRIBUTING guide found.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
77
No linter or formatter found.
→ Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.
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.
Lockfile present (Cargo.lock). Installs are reproducible.
Test files detected (crates/nub-cli/tests).
CI is configured (.github/workflows/ci.yml).
Project health
94
Dependency manifest found (Cargo.toml).
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)
- 12Forks
- 48Releaseslatest 2mo ago
Community
- -Community health
- -authors own >50% of commits
- 1,361Watchers
Responsiveness
- 2hMedian issue response
- 1hMedian PR merge time
- 1Open issues
Repository files38 root entries
- .agents
- .claude
- .githubGood: CI is configured (.github/workflows/ci.yml).
- benches
- benchmarks
- cratesGood: Test files detected (crates/nub-cli/tests).
- docker
- npm
- runtime
- scripts
- setup
- site
- skills
- stats
- tests
- vendorGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: Environment pinned via vendor/aube/packaging/copr/Dockerfile.Good: Dependabot is configured. Dependencies update automatically.Good: Security policy present.
- .dockerignore
- .gitignoreGood: .gitignore present.
- .gitmodules
- .vercelignore
- .worktreeinclude
- AGENTS.md
- bun.lock
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CLAUDE.md
- Cross.toml
- install.ps1
- install.sh
- L1_AGENTS.md
- LICENSEGood: Licensed under MIT.
- Makefile
- package-lock.json
- package.json
- pnpm-lock.yaml
- PROSE.md
- 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.
- skills-lock.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/nubjs/nub)