84
/ 100
Well engineered. The main gaps are issue and PR templates and CI.
A template for developers to start new UIs with Carbon, with Vite and server-side rendering, and a few more goodies
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 2CI/CD14pt
Add a lint step to catch style issues automatically.
- 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
README is present.
README documents how to install the project.
Licensed under Apache-2.0.
Contributing guide is detailed and thorough.
Engineering
76
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/buildTest.yml).
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (src/__tests__).
Linter or formatter configured (.stylelintrc.json).
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)
- 15Forks
- 3Releaseslatest 16d ago
Community
- 75% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 20Watchers
Responsiveness
- 40d 22hMedian issue response
- 24hMedian PR merge time
- 27Open issues
Repository files28 root entries
- .githubGood: Code of conduct present.Good: CI is configured (.github/workflows/buildTest.yml).
- .husky
- .vscode
- cspell-dictionaries
- docsGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.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.
- public
- scripts
- srcGood: Test files detected (src/__tests__).
- .gitignoreGood: .gitignore present.
- .lighthouserc.js
- .npmrc
- .nvmrcGood: Environment pinned via .nvmrc.
- .prettierignore
- .releaserc.json
- .stylelintignore
- .stylelintrc.jsonGood: Linter or formatter configured (.stylelintrc.json).
- .whitesource
- CHANGELOG.md
- cspell.json
- eslint.config.js
- index.html
- LICENSEGood: Licensed under Apache-2.0.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- prettier.config.js
- 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.
- renovate.json
- vite.config.js
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/carbon-design-system/carbon-react-router-starter)