0
/ 100
Getting noticed, but rough fundamentals could turn visitors away.
Jav 视频管理工具，包含：刮削，下载，播放。
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to C (75).
See your top fixesTop 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".
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues 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
41
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
Licensed under MIT.
Engineering
33
No linter or formatter found.
→ Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.
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 (vitest.config.ts).
CI is configured (.github/workflows/release.yml).
Lockfile present (bun.lock). Installs are reproducible.
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)
- 24Forks
- 16Releaseslatest 4mo ago
Community
- -Community health
- -authors own >50% of commits
- 274Watchers
Responsiveness
- 9hMedian issue response
- -Median PR merge time
- 0Open issues
Repository files23 root entries
- .claude
- .githubGood: CI is configured (.github/workflows/release.yml).
- .vscode
- docs
- public
- screenshot
- scripts
- src
- src-tauri
- .gitignoreGood: .gitignore present.
- bun.lockGood: Lockfile present (bun.lock). Installs are reproducible.
- CLAUDE.md
- components.json
- DEV.md
- index.html
- LICENSEGood: Licensed under MIT.
- package.jsonGood: Dependency manifest found (package.json).
- README.mdGood: README is present.Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.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.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Good: README documents how to run the project.
- TODO.md
- tsconfig.json
- tsconfig.node.json
- vite.config.ts
- vitest.config.tsGood: Test files detected (vitest.config.ts).
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/ddmoyu/javm)