95
/ 100
Excellent work. The main thing left to polish is a contributing guide.
Gunshi: Modern javascript command-line library
Outstanding. A score of 95/100 puts this repo in a very small tier of truly well-engineered projects.
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 2Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 3Reproducibility6pt
Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
- 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
89
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
99
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
Test files detected (bump.config.test.ts).
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (.editorconfig).
Issue or PR templates present.
Project health
95
Dependency manifest found (package.json).
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)
- 25Forks
- 108Releaseslatest 1y ago
Community
- 71% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 474Watchers
Responsiveness
- 2d 3hMedian issue response
- 2hMedian PR merge time
- 7Open issues
Repository files34 root entries
- .githooks
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Renovate is configured (.github/renovate.json). Dependencies update automatically across every package manager it detects.Good: Issue or PR templates present.
- .vscode
- assets
- bench
- design
- e2e
- packages
- playground
- scripts
- _typos.toml
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .npmignore
- .oxlintrc.json
- .prettierignore
- bump.config.test.tsGood: Test files detected (bump.config.test.ts).
- bump.config.ts
- CHANGELOG.md
- CLAUDE.md
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.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.
- eslint.config.ts
- knip.config.ts
- LICENSEGood: Licensed under MIT.
- NOTES.md
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- pnpm-workspace.yaml
- 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.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.Good: README documents how to run the project.
- tsconfig.ci.json
- tsconfig.json
- vitest.config.ts
- vitest.e2e.config.ts
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/kazupon/gunshi)