Getting noticed, but rough fundamentals could turn visitors away.
一款文字修仙小游戏
Documentation
69
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Engineering
20
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
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 (package-lock.json). Installs are reproducible.
Linter or formatter configured (.eslintrc.json).
Project health
73
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 (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)
- 35Forks
- 2Releaseslatest 6mo ago
Community
- —Community health
- —authors own >50% of commits
- 140Watchers
Responsiveness
- 1d 8hMedian issue response
- <1hMedian PR merge time
- 1Open issues
Repository files50 root entries
- .claude
- components
- constants
- docGood: 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.
- functions
- hooks
- party
- public
- scripts
- server
- services
- ssl
- store
- utils
- views
- .dockerignore
- .env.development
- .env.example
- .env.production
- .eslintignore
- .eslintrc.jsonGood: Linter or formatter configured (.eslintrc.json).
- .gitignoreGood: .gitignore present.
- .npmrc
- .prettierignore
- .prettierrc
- .vercelignore
- App.tsx
- docker-compose.full.yml
- docker-compose.yml
- DockerfileGood: Environment pinned via Dockerfile.
- Dockerfile.backend
- index.css
- index.html
- index.tsx
- Makefile
- metadata.json
- nginx.conf
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- partykit.json
- pnpm-lock.yaml
- postcss.config.js
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.
- tailwind.config.js
- tsconfig.json
- types.ts
- vercel.json
- vite-env.d.ts
- vite.config.ts
- wrangler.toml