Good shape overall. A few tweaks would push it into the top tier.
基于RSS的资讯聚合工作台
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 MIT.
Engineering
68
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.
CI is configured (.github/workflows/dockerhub-images.yml).
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (src/app/api/admin/settings/model-api-configs/[id]/test).
Linter or formatter configured (eslint.config.mjs).
Project health
89
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)
- 17Forks
- 13Releaseslatest 5d ago
Community
- —Community health
- —authors own >50% of commits
- 248Watchers
Responsiveness
- 3hMedian issue response
- 7hMedian PR merge time
- 0Open issues
Repository files26 root entries
- .githubGood: CI is configured (.github/workflows/dockerhub-images.yml).
- docs
- imgs
- prisma
- public
- scripts
- srcGood: Test files detected (src/app/api/admin/settings/model-api-configs/[id]/test).
- tests
- .dockerignore
- .env.docker.example
- .env.example
- .gitignoreGood: .gitignore present.
- AGENTS.md
- CLAUDE.md
- docker-compose.yml.example
- DockerfileGood: Environment pinned via Dockerfile.
- eslint.config.mjsGood: Linter or formatter configured (eslint.config.mjs).
- LICENSEGood: Licensed under MIT.
- next.config.ts
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- postcss.config.mjs
- 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.
- tsconfig.json
- vitest.config.ts
- vitest.setup.ts