94
/ 100
Polished and well engineered. Punching above its star count.
The open creative AI workspace
Top fixes
Highest-impact changes first, ranked by point weight
- 1Dependency manifest6pt
Add a one-line description to package.json. It appears in npm search and on GitHub.
- 2Dependency manifest6pt
Add a `repository` field pointing to the GitHub URL so npm knows where the source lives.
- 3Dependency manifest6pt
Add a `keywords` array to help people find your package on npm.
- 4Dependency manifest6pt
Add a `homepage` field pointing to your docs or project website.
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
88
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README is present.
README documents how to install the project.
Licensed under AGPL-3.0.
Engineering
100
Test files detected (docs/nodes/nodetool/test).
CI is configured (.github/workflows/test-coverage.yaml).
Linter or formatter configured (.prettierrc).
Lockfile present (package-lock.json). Installs are reproducible.
Issue or PR templates present.
Project health
89
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)
- 54Forks
- 118Releaseslatest 6mo ago
Community
- 37% - WeakCommunity health
- -authors own >50% of commits
- 409Watchers
Responsiveness
- 3hMedian issue response
- 3hMedian PR merge time
- 30Open issues
Repository files47 root entries
- .claude
- .deploy
- .design-sync
- .githubGood: CI is configured (.github/workflows/test-coverage.yaml).Good: Dependabot covers 5 ecosystems (npm, npm, npm, npm, github-actions). Dependencies stay current.Good: Issue or PR templates present.
- .jules
- .vscode
- chrome-extension
- demo
- docsGood: Test files detected (docs/nodes/nodetool/test).
- electron
- examples
- marketing
- mobile
- packages
- scripts
- web
- workspace
- .agents
- .cursorignore
- .dockerignore
- .env.example
- .gitignoreGood: .gitignore present.
- .nvmrc
- .oxlintrc.json
- .prettierrcGood: Linter or formatter configured (.prettierrc).
- AGENTS.md
- ARCHITECTURE.md
- CHANGELOG.md
- CLAUDE.md
- deploy.sh
- DockerfileGood: Environment pinned via Dockerfile.
- eslint.config.mjs
- install.sh
- LICENSE.txtGood: Licensed under AGPL-3.0.
- MANIFEST.in
- MANIFESTO.md
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- react-doctor.config.json
- README.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.
- screen_canvas.png
- screen_video_editor.png
- skills-lock.json
- tsconfig.base.json
- tsconfig.build.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/nodetool-ai/nodetool)