Strong community interest, but tests, CI, or docs need work.
Documentation
52
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Engineering
39
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
CI is configured (.github/workflows/build-modules-and-alert.yml).
Linter or formatter configured (eslint.config.js).
Project health
73
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Dependency manifest found (package.json).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 7,372Forks
- 1Releaseslatest 8mo ago
Community
- —Community health
- —authors own >50% of commits
- 1,206Watchers
Responsiveness
- 6hMedian issue response
- 8hMedian PR merge time
- 106Open issues
Repository files19 root entries
- .githubGood: CI is configured (.github/workflows/build-modules-and-alert.yml).
- cex
- projects
- registries
- scripts
- skills
- typings
- utils
- .gitignoreGood: .gitignore present.
- .prettierignore
- env.sample
- eslint.config.jsGood: Linter or formatter configured (eslint.config.js).
- funding.json
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- pnpm-workspace.yaml
- pull_request_template.md
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: 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.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.
- test.js