95

/ 100

GradeA

Excellent work. The main thing left to polish is CI.

Top 10% of 5,156 graded repos

Bring Tailwind CSS to every platform! 把 Tailwind CSS 的原子化开发体验带到全端!

TypeScript1,863MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

9 to address
  1. 1
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  2. 2
    CI/CD14pt

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

  3. 3
    Install and run instructions9pt

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

  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

91

Contributing guide5pt60

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

92

CI/CD14pt72

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

Tests18pt100

Test files detected (apps/lynx-promo-video/src/components/Typing.test.ts).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Reproducibility6pt100

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 86 / 495
    Commits (30d / 90d)
  • 103
    Forks
  • 1000
    Releaseslatest 2y ago

Community

  • 85% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 1,863
    Watchers

Responsiveness

  • <1h
    Median issue response
  • <1h
    Median PR merge time
  • 19
    Open issues
Repository files63 root entries
  • .agents
  • .changeset
  • .claude
  • .codegraph
    Good: .gitignore present.
  • .codex
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
  • .husky
  • .kiro
  • .vscode
  • apps
    Good: Test files detected (apps/lynx-promo-video/src/components/Typing.test.ts).
  • assets
  • benchmark
  • demo
    Issue: Build artifacts or local files may be committed (demo/weapp-vite-tailwindcss-v4/.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • docs
  • e2e
  • examples
  • packages
  • packages-runtime
  • patches
  • reports
  • research
  • scripts
  • skills
  • starter
  • submodules
  • talk
  • templates
  • tools
  • website
  • .dockerignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
  • .gitmodules
  • .npmrc
  • .nvmrc
  • .pnpmfile.cjs
  • .prettierrc
  • AGENTS.md
  • CHANGELOG.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • commitlint.config.ts
  • 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).
    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.
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • eslint.config.js
  • LICENSE
    Good: Licensed under MIT.
  • lint-staged.config.js
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • README_en.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.
  • README.md
  • renovate.json
    Good: Renovate is configured (renovate.json). Dependencies update automatically across every package manager it detects.
  • repoctl.config.ts
  • SECURITY.md
    Good: Security policy present.
  • sonar-project.properties
  • stylelint.config.js
  • templates.jsonc
  • tsconfig.all.json
  • tsconfig.json
  • turbo.json
  • 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/sonofmagic/weapp-tailwindcss)](https://www.repo-grade.com/report/sonofmagic/weapp-tailwindcss)

More graded TypeScript repos