95
/ 100
Excellent work. The main thing left to polish is CI.
Bring Tailwind CSS to every platform! 把 Tailwind CSS 的原子化开发体验带到全端!
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 2CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Contributing 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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
91
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.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
92
CI is configured (.github/workflows/ci.yml).
Test files detected (apps/lynx-promo-video/src/components/Typing.test.ts).
Linter or formatter configured (.editorconfig).
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
Issue or PR templates present.
Project health
94
.gitignore present.
Dependency manifest found (package.json).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 86 / 495Commits (30d / 90d)
- 103Forks
- 1000Releaseslatest 2y ago
Community
- 85% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 1,863Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 19Open issues
Repository files63 root entries
- .agents
- .changeset
- .claude
- .codegraphGood: .gitignore present.
- .codex
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Issue or PR templates present.
- .husky
- .kiro
- .vscode
- appsGood: Test files detected (apps/lynx-promo-video/src/components/Typing.test.ts).
- assets
- benchmark
- demoIssue: 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
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitattributes
- .gitignore
- .gitmodules
- .npmrc
- .nvmrc
- .pnpmfile.cjs
- .prettierrc
- AGENTS.md
- CHANGELOG.md
- CLAUDE.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- commitlint.config.ts
- CONTRIBUTING.mdIssue: 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.
- DockerfileGood: Environment pinned via Dockerfile.
- eslint.config.js
- LICENSEGood: Licensed under MIT.
- lint-staged.config.js
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- pnpm-workspace.yaml
- README_en.mdGood: 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.jsonGood: Renovate is configured (renovate.json). Dependencies update automatically across every package manager it detects.
- repoctl.config.ts
- SECURITY.mdGood: Security policy present.
- sonar-project.properties
- stylelint.config.js
- templates.jsonc
- tsconfig.all.json
- tsconfig.json
- turbo.json
- vitest.config.ts
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/sonofmagic/weapp-tailwindcss)