Good shape overall. A few tweaks would push it into the top tier.
Fixes prompt cache regression in Claude Code that causes up to 20x cost increase on resumed sessions
Documentation
85
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README documents how to install the project.
README is present.
Licensed under Other.
Engineering
62
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.
No dependency lockfile found (−70 pts).
→ Commit package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lock so Node installs are repeatable.
CI is configured (.github/workflows/test-shim.yml).
Test files detected (test).
Project health
97
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)
- 22Forks
- 43Releaseslatest 2mo ago
Community
- —Community health
- —authors own >50% of commits
- 309Watchers
Responsiveness
- 2hMedian issue response
- 1hMedian PR merge time
- 28Open issues
Repository files25 root entries
- .claude
- .githubGood: CI is configured (.github/workflows/test-shim.yml).
- bin
- docs
- hooks
- proxy
- templates
- testGood: Test files detected (test).
- tools
- .dockerignore
- .gitignoreGood: .gitignore present.
- AGENTS.md
- CHANGELOG.md
- claude-fixed.bat
- CLAUDE.md
- DockerfileGood: Environment pinned via Dockerfile.
- insertion.txt
- LICENSEGood: Licensed under Other.
- package.jsonGood: Dependency manifest found (package.json).
- postinstall.js
- preload.mjs
- README.ko.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.
- README.md
- README.zh.md
- THIRD_PARTY_LICENSES