90
/ 100
Excellent work. The main thing left to polish is CI. It just hasn't found an audience yet.
Develop. Preview. Ship.
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 2CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 4README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
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
93
CONTRIBUTING guide found.
README is present.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
91
CI is configured (.github/workflows/test-lint.yml).
Lockfile present (Cargo.lock). Installs are reproducible.
Test files detected (examples/__tests__).
Linter or formatter configured (.editorconfig).
Issue or PR templates present.
Project health
89
Dependency manifest found (Cargo.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 0 / 0Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 0Watchers
Responsiveness
- -Median issue response
- 1d 4hMedian PR merge time
- 50Open issues
Repository files35 root entries
- .changeset
- .githubGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: Code of conduct present.Good: CI is configured (.github/workflows/test-lint.yml).Good: Issue or PR templates present.
- .husky
- api
- crates
- errors
- examplesGood: Test files detected (examples/__tests__).Good: Environment pinned via examples/react-router/Dockerfile.
- internals
- packagesGood: Dependabot is configured. Dependencies update automatically.
- scripts
- test
- utils
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .eslintignore
- .gitattributes
- .gitignoreGood: .gitignore present.
- .node_version
- .npmrc
- .nvmrc
- .prettierignore
- .vercel.approvers
- .vercelignore
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- DEVELOPING_A_RUNTIME.md
- LICENSEGood: Licensed under Apache-2.0.
- package.json
- pnpm-lock.yaml
- 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.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.
- test-cursor-detection.js
- tsconfig.base.json
- turbo.json
- vercel.json
- vitest.config.mts
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/finaljrad-ir/vercel)