kazupon/gunshi

0

/ 100

Documentation89
Engineering96
Health95
TypeScript425MIT1d ago
Grade a repo

Polished and well engineered. Punching above its star count.

Gunshi: Modern javascript command-line library

Documentation

89

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

96

Reproducibility6pt70

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

Tests18pt100

Test files detected (e2e/bun.spec.ts).

CI/CD14pt100

CI is configured (.github/workflows/ci.yml).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

95

Dependency manifest6pt85

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 23
    Forks
  • 98
    Releaseslatest 1y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 425
    Watchers

Responsiveness

  • 1d 3h
    Median issue response
  • 2h
    Median PR merge time
  • 17
    Open issues
Repository files32 root entries
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
  • .vscode
  • assets
  • bench
  • design
  • e2e
    Good: Test files detected (e2e/bun.spec.ts).
  • packages
  • playground
  • scripts
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .npmignore
  • .npmrc
  • .oxlintrc.json
  • .prettierignore
  • CHANGELOG.md
  • CLAUDE.md
  • CONTRIBUTING.md
    Good: 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
  • LICENSE
    Good: Licensed under MIT.
  • NOTES.md
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • README.md
    Good: 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