0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
基于Goalng、Gin、Casbin & Vue3、TypeScript、Element Plus、Pinia 的前后端分离的动态路由权限管理系统
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2README12pt
Link to a deployed version, docs site, or demo video. Users want to see it running.
- 3README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 4Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
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
70
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 MIT.
Engineering
78
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 (server/internal/pkg/cron/job_test.go).
Lockfile present (server/go.sum). Installs are reproducible.
CI is configured (web/.github/workflows/deploy.yml).
Linter or formatter configured (web/.editorconfig).
Project health
94
.gitignore present.
Dependency manifest found (server/go.mod).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 24Forks
- 10Releaseslatest 3mo ago
Community
- -Community health
- -authors own >50% of commits
- 112Watchers
Responsiveness
- 15d 21hMedian issue response
- 29d 9hMedian PR merge time
- 0Open issues
Repository files12 root entries
- .opencode
- .sisyphus
- docker-composeGood: Environment pinned via docker-compose/compose.yml.
- img
- openspec
- serverGood: Test files detected (server/internal/pkg/cron/job_test.go).Good: Lockfile present (server/go.sum). Installs are reproducible.Good: Dependency manifest found (server/go.mod).
- webGood: CI is configured (web/.github/workflows/deploy.yml).Good: Linter or formatter configured (web/.editorconfig).Issue: Build artifacts or local files may be committed (web/.env) (−40 pts).Fix: Remove them and add to .gitignore.
- .gitignoreGood: .gitignore present.
- AGENTS.md
- LICENSEGood: Licensed under MIT.
- README.en.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.Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.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.
- README.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/pddzl/td27-admin)