daangn/seed-design

0

/ 100

Documentation45
Engineering52
Health89
TypeScript889Apache-2.01d ago
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

The Seed Design System

Documentation

45

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt30

README is present.

Install and run instructions9pt55

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

→ Add a section showing how to install dependencies.

License6pt100

Licensed under Apache-2.0.

Engineering

52

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 (docs/app/_llms/normalize-llm-body.pipeline.test.ts).

CI/CD14pt68

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

Reproducibility6pt80

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

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

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

  • —
    Commits (30d / 90d)
  • 57
    Forks
  • 843
    Releaseslatest 3y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 889
    Watchers

Responsiveness

  • 2h
    Median issue response
  • <1h
    Median PR merge time
  • 46
    Open issues
Repository files37 root entries
  • .agents
  • .changeset
  • .claude
  • .github
    Good: CI is configured (.github/workflows/cli-test.yml).
  • .vscode
  • docs
    Good: Test files detected (docs/app/_llms/normalize-llm-body.pipeline.test.ts).
  • 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.
  • AGENTS.md
  • biome.json
  • bun.lock
    Good: Lockfile present (bun.lock). Installs are reproducible.
  • bunfig.toml
  • CLAUDE.md
  • cover.png
  • 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 is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown 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.
    Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.
    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
  • TECH.md
  • tsconfig.headless.json
  • tsconfig.json