0
/ 100
Solid engineering. The biggest lever is test coverage.
Next generation frontend tooling. It's fast!
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
Show a quick-start snippet so contributors can see what using your project looks like.
- 3Install and run instructions9pt
Add a section showing how to install dependencies.
- 4Install and run instructions9pt
Add a section showing how to start or use the project.
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
65
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Contributing guide is detailed and thorough.
Licensed under MIT.
Engineering
74
Test files detected (packages/create-vite/__tests__).
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (.editorconfig).
Issue or PR templates present.
Project health
92
Actively maintained (pushed within 3 months).
Dependency manifest found (package.json).
Repository has a description.
.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
- 0Watchers
Responsiveness
- -Median issue response
- 1d 4hMedian PR merge time
- 6Open issues
Repository files24 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Renovate config present (.github/renovate.json5).Good: Issue or PR templates present.
- .stackblitz
- docs
- packagesGood: Test files detected (packages/create-vite/__tests__).
- patches
- playground
- scripts
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .git-blame-ignore-revs
- .gitattributes
- .gitignoreGood: .gitignore present.
- .prettierignore
- .prettierrc.json
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Good: Contributing guide describes code style expectations.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- eslint.config.js
- LICENSEGood: Licensed under MIT.
- netlify.toml
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- 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.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Good: README links to a live demo or deployed app.Good: README includes status badges.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- vitest.config.e2e.ts
- 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/finaljrad-ir/vite)