carbon-design-system/carbon-react-router-starter

0

/ 100

Documentation93
Engineering76
Health89
JavaScript19Apache-2.0today
Grade a repo

Solid foundation. Invest in docs and CI to grow from here.

A template for developers to start new UIs with Carbon, with Vite and server-side rendering, and a few more goodies

Documentation

93

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Contributing guide5pt100

Contributing guide is detailed and thorough.

Engineering

76

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.

CI/CD14pt68

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

Reproducibility6pt80

Lockfile present (package-lock.json). Installs are reproducible.

Tests18pt100

Test files detected (src/__tests__).

Linting and formatting5pt100

Linter or formatter configured (.stylelintrc.json).

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)
  • 14
    Forks
  • 0
    Releases

Community

  • 75% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 19
    Watchers

Responsiveness

  • 18d 5h
    Median issue response
  • 24h
    Median PR merge time
  • 20
    Open issues
Repository files25 root entries
  • .github
    Good: Code of conduct present.
    Good: CI is configured (.github/workflows/buildTest.yml).
  • .husky
  • .vscode
  • cspell-dictionaries
  • docs
    Good: 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
  • src
    Good: Test files detected (src/__tests__).
  • .gitignore
    Good: .gitignore present.
  • .lighthouserc.js
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • .prettierignore
  • .stylelintignore
  • .stylelintrc.json
    Good: Linter or formatter configured (.stylelintrc.json).
  • .whitesource
  • cspell.json
  • eslint.config.js
  • index.html
  • LICENSE
    Good: Licensed under Apache-2.0.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • prettier.config.js
  • 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.
    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