A top-tier open source project. Docs, tests, and CI are all in excellent shape.
Ergonomic Framework for Humans
Documentation
62
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README is present.
Licensed under MIT.
Engineering
94
CI is configured (.github/workflows/ci.yml).
Lockfile present (bun.lock). Installs are reproducible.
Test files detected (test).
Linter or formatter configured (.eslintrc.json).
Issue or PR templates present.
Project health
100
Dependency manifest found (package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 543Forks
- 106Releaseslatest 2y ago
Community
- 62% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 18,547Watchers
Responsiveness
- 4d 21hMedian issue response
- 1d 15hMedian PR merge time
- 344Open issues
Repository files21 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Dependabot covers 2 ecosystems (npm, github-actions). Dependencies stay current.Good: Issue or PR templates present.
- example
- src
- testGood: Test files detected (test).
- .eslintrc.jsonGood: Linter or formatter configured (.eslintrc.json).
- .gitignoreGood: .gitignore present.
- .npmignore
- .npmrc
- .prettierrc
- build.ts
- bun.lockGood: Lockfile present (bun.lock). Installs are reproducible.
- CHANGELOG.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdIssue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.Good: Contributing guide includes setup/install instructions.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.
- knip.json
- LICENSEGood: Licensed under MIT.
- package.jsonGood: Dependency manifest found (package.json).
- README.mdGood: README is present.Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- tsconfig.dts.json
- tsconfig.json
- tsconfig.test.json