93/ 100 · A
A top-tier open source project. Docs, tests, and CI are all in excellent shape.
A JS library for predictable global state management
TypeScript61,496 starsMITupdated 4d ago
DocumentationREADME, setup, examples, license
EngineeringTests, CI, linting, lockfiles
Project healthDescription, activity, stars, deps
What to fix first
The highest-impact improvements for this repo.
- 1CI/CDEngineeringInfo
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 2CI/CDEngineeringInfo
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 3READMEDocumentationWarning
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
Detailed breakdown
Documentation
89- README80
- README is present.
- README is well structured with multiple sections.
- No screenshots or images in the README (−20 pts).Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- README has code examples.
- README links to a live demo or deployed app.
- README includes status badges.
- Install and run instructions90
- README documents how to install the project.
- README documents how to run the project.
- If your project uses environment variables, add a .env.example listing them (+10 pts).Add a .env.example listing all required environment variables so contributors know what to set up.
- License100
- Licensed under MIT.
- Contributing guide95
- Contributing guide is detailed and thorough.
- Contributing guide includes setup/install instructions.
- Contributing guide lacks a code style section (−8 pts).Describe your linting/formatting rules and how to run them (e.g. npm run lint, ruff check .).
- Contributing guide explains how to run tests.
- Contributing guide describes the PR/review workflow.
- Contributing guide includes code examples.
- Code of conduct present.
Engineering
93- Tests100
- Test files detected (examples/counter-ts/src/App.test.tsx).
- CI/CD100
Not applicable?
- CI is configured (.github/workflows/test.yaml).
- CI workflow runs tests.
- CI runs on pull requests, not just on pushes to main.
- CI workflow runs a lint or format check.
- Optional: add type checking to CI.Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- Optional: report test coverage in CI.Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- CI caches dependencies for faster runs.
- CI tests across multiple environments or versions.
- CI includes a build step.
- Linting and formatting75
- Linter or formatter configured (.editorconfig).
- Lint script wired into package.json.
- tsconfig.json does not enable strict type checking (−20 pts).Add "strict": true to compilerOptions to catch more bugs at compile time.
- Reproducibility70
- Lockfile present (yarn.lock). Installs are reproducible.
- No Dockerfile or runtime version pin found. Adding one earns +10 pts.Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
- No Dependabot config (adding it earns up to +20 pts).Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
- Issue and PR templates90
- Issue or PR templates present.
- Optional: add a SECURITY.md.A SECURITY.md explains how to responsibly disclose vulnerabilities. Worth adding once the project has real users.
Project health
100- Dependency manifest100
- Dependency manifest found (package.json).
- package.json has a description field.
- package.json links back to the repository.
- Repository metadata100
- Repository has a description.
- Primary language detected: TypeScript.
- package.json metadata is complete (description, keywords, repository).
- Activity100
- Actively maintained (pushed within the last month).
- 61,496 stars.
- Housekeeping100
- .gitignore present.
Repository files37 root entries
- .githubGood: CI is configured (.github/workflows/test.yaml).Good: Issue or PR templates present.
- .yarn
- docs
- examplesGood: Test files detected (examples/counter-ts/src/App.test.tsx).
- logo
- scripts
- src
- test
- website
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .eslintignore
- .eslintrc.cjs
- .git-blame-ignore-revs
- .gitattributes
- .gitbook.yaml
- .gitignoreGood: .gitignore present.
- .prettierrc.json
- .release-it.json
- .yarnrc.yml
- CHANGELOG.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Info: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them (e.g. npm run lint, ruff check .).Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- CNAME
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.md
- errors.json
- LICENSE-logo.md
- LICENSE.mdGood: Licensed under MIT.
- netlify.toml
- package.jsonGood: Dependency manifest found (package.json).
- PATRONS.md
- README.mdGood: README is present.Good: README is well structured with multiple sections.Warning: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.
- tsconfig.base.json
- tsconfig.build.json
- tsconfig.json
- tsconfig.test.json
- tsup.config.ts
- vitest.config.mts
- yarn.lockGood: Lockfile present (yarn.lock). Installs are reproducible.