90
/ 100
Excellent work. The main thing left to polish is issue and PR templates.
Your Software Factory - build faster and better with multi node agents that work 24/7
Top fixes
Highest-impact changes first, ranked by point weight
- 1Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 2Issue and PR templates6pt
Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
- 3Dependency manifest6pt
Add a one-line description to package.json. It appears in npm search and on GitHub.
- 4Dependency manifest6pt
Add a `keywords` array to help people find your package on npm.
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
96
README documents how to install the project.
Contributing guide is detailed and thorough.
README is present.
Licensed under MIT.
Engineering
88
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.
Test files detected (packages/cli/src/__tests__).
CI is configured (.github/workflows/test-release.yml).
Linter or formatter configured (eslint.config.mjs).
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
Project health
94
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
- 125 / 1423Commits (30d / 90d)
- 169Forks
- 108Releaseslatest 5mo ago
Community
- 62% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 1,302Watchers
Responsiveness
- <1hMedian issue response
- 4hMedian PR merge time
- 97Open issues
Repository files39 root entries
- .changeset
- .githubGood: CI is configured (.github/workflows/test-release.yml).Good: Dependabot covers 2 ecosystems (github-actions, npm). Dependencies stay current.
- audit
- demo
- docsGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.Good: Contributing guide explains how to run tests.Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.Good: Contributing guide includes code examples.
- packagesGood: Test files detected (packages/cli/src/__tests__).
- plugins
- reports
- screenshots
- scripts
- .dockerignore
- .gitattributes
- .gitignoreGood: .gitignore present.
- AGENTS.md
- CHANGELOG-archive.md
- CHANGELOG.md
- CLAUDE.md
- CONCEPTS.md
- DockerfileGood: Environment pinned via Dockerfile.
- eslint.config.mjsGood: Linter or formatter configured (eslint.config.mjs).
- i18next.config.ts
- LICENSEGood: Licensed under MIT.
- MOBILE.md
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- pnpm-workspace.yaml
- README.es.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.fr.md
- README.ko.md
- README.md
- README.pt-BR.md
- README.zh-CN.md
- README.zh-TW.md
- RELEASING.md
- ROADMAP.md
- STRATEGY.md
- tsconfig.base.json
- tsconfig.json
- tsconfig.placeholder.d.ts
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/runfusion/fusion)