92
/ 100
A well-known project done right. Strong docs and solid engineering throughout.
SSH workspace, SFTP, and terminals in one
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.
- 2Reproducibility6pt
Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
- 3Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
- 4Dependency manifest6pt
Add a `repository` field pointing to the GitHub URL so npm knows where the source lives.
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
85
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 documents how to install the project.
README is present.
Licensed under GPL-3.0.
Engineering
96
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (application/AppHandlers.connect.test.ts).
CI is configured (.github/workflows/build-et-binaries.yml).
Linter or formatter configured (eslint.config.js).
Issue or PR templates present.
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
- 427 / 896Commits (30d / 90d)
- 259Forks
- 136Releaseslatest 7mo ago
Community
- 42% - WeakCommunity health
- -authors own >50% of commits
- 2,738Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 56Open issues
Repository files41 root entries
- .githubGood: CI is configured (.github/workflows/build-et-binaries.yml).Good: Issue or PR templates present.
- .vscode
- applicationGood: Test files detected (application/AppHandlers.connect.test.ts).
- build
- components
- docs
- domain
- electron
- infrastructure
- lib
- patches
- public
- resources
- screenshots
- scripts
- skills
- types
- .gitattributes
- .gitignoreGood: .gitignore present.
- .npmrc
- AGENTS.md
- App.tsx
- CHANGELOG.md
- CLAUDE.md
- electron-builder.config.cjs
- eslint.config.jsGood: Linter or formatter configured (eslint.config.js).
- ET_INTEGRATION_CHECKLIST.md
- global.d.ts
- index.css
- index.html
- index.tsx
- LICENSEGood: Licensed under GPL-3.0.
- metadata.json
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- README.ja-JP.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.md
- README.zh-CN.md
- tsconfig.json
- types.ts
- vite.config.ts
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/binaricat/netcatty)