0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
基于 Incus 的 LXC / KVM NAT VPS 销售、交付与管理面板。
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".
- 2README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 3Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
- 4Issue and PR templates6pt
Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
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
81
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Licensed under BSD-3-Clause.
Engineering
61
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.
Test files detected (agent/internal/config/config_test.go).
Lockfile present (package-lock.json). Installs are reproducible.
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (client/eslint.config.js).
Project health
92
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)
- 105Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 126Watchers
Responsiveness
- <1hMedian issue response
- -Median PR merge time
- 0Open issues
Repository files20 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- agentGood: Test files detected (agent/internal/config/config_test.go).
- clientGood: Linter or formatter configured (client/eslint.config.js).
- scripts
- server
- .dockerignore
- .env.example
- .gitattributes
- .gitignoreGood: .gitignore present.
- AGENTS.md
- docker-compose.dev.yml
- docker-compose.yml
- DockerfileGood: Environment pinned via Dockerfile.
- LICENSEGood: Licensed under BSD-3-Clause.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yaml
- 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.
- TransparentProxy.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/qwer-xyz/incudal)