dalestudy/daleui
Grade a repo

93

/ 100

GradeA

Well engineered for its size. A portfolio piece worth showing off.

Top 8% of 5,156 graded repos

๐ŸŽจ ๋””์ž์ธ ์‹œ์Šคํ…œ

Documentation90
Engineering99
Health81
TypeScript93MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

10 to address
  1. 1
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  2. 2
    Reproducibility6pt

    Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.

  3. 3
    Dependency manifest6pt

    Add a one-line description to package.json. It appears in npm search and on GitHub.

  4. 4
    Contributing guide5pt

    Add setup instructions, code style notes, and how to run tests.

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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

90

Contributing guide5pt52

CONTRIBUTING guide is very brief (โˆ’12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

โ†’ Add setup instructions, code style notes, and how to run tests.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

99

Reproducibility6pt90

Lockfile present (bun.lock). Installs are reproducible.

Tests18pt100

Test files detected (src/components/Box/Box.test.tsx).

CI/CD14pt100

CI is configured (.github/workflows/integration.yml).

Linting and formatting5pt100

Linter or formatter configured (.prettierrc).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

81

Repository metadata5pt40

No repository description set on GitHub (โˆ’60 pts).

โ†’ Add a one-line description in the repo Settings โ†’ About. It appears in search results and social previews.

Dependency manifest6pt90

Dependency manifest found (package.json).

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 29 / 126
    Commits (30d / 90d)
  • 8
    Forks
  • 12
    Releaseslatest 3mo ago

Community

  • 100% - Good
    Community health
  • 3 bus factor
    authors own >50% of commits
  • 93
    Watchers

Responsiveness

  • 10d 6h
    Median issue response
  • 23h
    Median PR merge time
  • 101
    Open issues
Repository files27 root entries
  • .github
    Good: CI is configured (.github/workflows/integration.yml).
    Good: Dependabot covers 2 ecosystems (bun, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • .storybook
  • public
  • src
    Good: Test files detected (src/components/Box/Box.test.tsx).
  • .all-contributorsrc
  • .gitignore
    Good: .gitignore present.
  • .prettierignore
  • .prettierrc
    Good: Linter or formatter configured (.prettierrc).
  • bun.lock
    Good: Lockfile present (bun.lock). Installs are reproducible.
  • chromatic.config.json
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • codecov.yml
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (โˆ’12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    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.
    Issue: Contributing guide lacks a testing section (โˆ’8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Issue: Contributing guide lacks a PR workflow section (โˆ’8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (โˆ’5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • eslint.config.js
  • LICENSE
    Good: Licensed under MIT.
  • package.json
    Good: Dependency manifest found (package.json).
  • panda.config.ts
  • postcss.config.cjs
  • README.md
    Good: 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • tsconfig.app.json
  • tsconfig.build.json
  • tsconfig.json
  • tsconfig.node.json
  • vite.config.ts
  • vite.lib.config.ts
  • vitest.config.ts
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/dalestudy/daleui)](https://www.repo-grade.com/report/dalestudy/daleui)

More graded TypeScript repos