0
/ 100
Good community traction and solid fundamentals. Nearly in the top tier.
A UI toolkit for building accessible web apps and design systems with SolidJS.
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a lint step to catch style issues automatically.
- 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 a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
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
92
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
CI is configured (.github/workflows/build.yml).
Test files detected (packages/core/src/accordion/accordion.test.tsx).
Linter or formatter configured (.editorconfig).
Issue or PR templates present.
Project health
95
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)
- 111Forks
- 85Releaseslatest 3y ago
Community
- -Community health
- -authors own >50% of commits
- 1,793Watchers
Responsiveness
- 11hMedian issue response
- <1hMedian PR merge time
- 132Open issues
Repository files24 root entries
- .changeset
- .githubGood: CI is configured (.github/workflows/build.yml).Good: Issue or PR templates present.
- apps
- packagesGood: Test files detected (packages/core/src/accordion/accordion.test.tsx).
- templates
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitignoreGood: .gitignore present.
- .gitpod.yml
- .npmrc
- .prettierignore
- .prettierrc.json
- biome.json
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- commitlint.config.js
- 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.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- LICENSE.mdGood: Licensed under MIT.
- netlify.toml
- NOTICE.txt
- 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.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.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.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.
- tsconfig.json
- turbo.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/kobaltedev/kobalte)