0
/ 100
Solid early foundation. Docs and CI will help it get noticed.
AI舆情分析系统
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
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 3README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 4Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
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
73
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.
A license file is present.
Engineering
80
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
Test files detected (MediaCrawler/test).
Lockfile present (MediaCrawler/package-lock.json). Installs are reproducible.
CI is configured (MediaCrawler/.github/workflows/deploy.yml).
Issue or PR templates present.
Project health
84
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 (MediaCrawler/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)
- 0Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 5Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 0Open issues
Repository files15 root entries
- backendGood: Environment pinned via backend/Dockerfile.
- bin
- docs
- frontend
- frontend-admin
- MediaCrawlerGood: A license file is present.Good: Test files detected (MediaCrawler/test).Good: CI is configured (MediaCrawler/.github/workflows/deploy.yml).Good: Lockfile present (MediaCrawler/package-lock.json). Installs are reproducible.Good: Issue or PR templates present.Good: Dependency manifest found (MediaCrawler/package.json).
- rag
- scripts
- .gitignoreGood: .gitignore present.
- CLAUDE.md
- docker-compose.yml
- Makefile
- 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.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.
- start.bat
- workflow-architecture.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/leozeng-coder/opinion_analysis)