daangn/seed-design
Grade a repo

66

/ 100

GradeD

A workable base with real gaps. Start with test coverage and issue and PR templates.

Top 50% of 5,156 graded repos

SEED Design System

Documentation70
Engineering55
Health89
TypeScript1,119Apache-2.010d ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (86).

See your top fixes
Now
D
66
Potential
B
86

Top fixes

Highest-impact changes first, ranked by point weight

20 to address
  1. 1
    Tests18pt

    Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".

  2. 2
    CI/CD14pt

    Add `pull_request:` to the workflow `on:` triggers.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

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

70

Install and run instructions9pt55

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

Contributing guide5pt64

Contributing guide is detailed and thorough.

README12pt68

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

55

Issue and PR templates6pt0

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.

Tests18pt35

Test files detected (.github/scripts/bump-peer-deps.test.ts).

CI/CD14pt68

CI is configured (.github/workflows/cli-test.yml).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Reproducibility6pt100

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

Project health

89

Dependency manifest6pt65

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 175 / 469
    Commits (30d / 90d)
  • 93
    Forks
  • 998
    Releaseslatest 3y ago

Community

  • 50% - Fair
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 1,119
    Watchers

Responsiveness

  • 1d 4h
    Median issue response
  • <1h
    Median PR merge time
  • 71
    Open issues
Repository files40 root entries
  • .agents
  • .changeset
  • .claude
  • .github
    Good: Test files detected (.github/scripts/bump-peer-deps.test.ts).
    Good: CI is configured (.github/workflows/cli-test.yml).
  • .vscode
  • docs
  • ecosystem
  • examples
  • packages
  • patches
  • scripts
  • skills
  • tools
  • types
  • .coderabbit.yaml
  • .cursorignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mcp.json
  • .npmrc
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • .ultraignore
  • AGENTS.md
  • ARCHITECTURE.md
  • biome.json
  • bun.lock
    Good: Lockfile present (bun.lock). Installs are reproducible.
  • bunfig.toml
  • CLAUDE.md
  • CONTRIBUTING.md
    Good: 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.
    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.
    Good: Contributing guide includes code examples.
  • cover.webp
  • knip.json
  • LICENSE
    Good: Licensed under Apache-2.0.
  • NOTICE
  • package.json
    Good: Dependency manifest found (package.json).
  • README.md
    Good: README is present.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    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.
    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.
  • renovate.json
    Good: Renovate is configured (renovate.json). Dependencies update automatically across every package manager it detects.
  • TECH.md
  • tsconfig.headless.json
  • tsconfig.json
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/daangn/seed-design)](https://www.repo-grade.com/report/daangn/seed-design)

More graded TypeScript repos