72
/ 100
Solid engineering. The biggest lever is CI.
An AI agent that claws through your network
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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
81
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.
Licensed under Apache-2.0.
Engineering
55
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
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.
CI is configured (.github/workflows/skill-review.yml).
Test files detected (mcp-servers/eve-ng-mcp-server/tests).
Lockfile present (mcp-servers/azure-network-mcp/requirements.txt). Installs are reproducible.
Project health
100
Dependency manifest found (mcp-servers/azure-network-mcp/requirements.txt).
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 / 138Commits (30d / 90d)
- 168Forks
- 0Releases
Community
- 42% - WeakCommunity health
- -authors own >50% of commits
- 611Watchers
Responsiveness
- 15hMedian issue response
- <1hMedian PR merge time
- 0Open issues
Repository files36 root entries
- .githubGood: CI is configured (.github/workflows/skill-review.yml).
- .specify
- benchmarks
- config
- docs
- examples
- labGood: Environment pinned via lab/frr-testbed/docker-compose.yml.
- mcp-serversGood: Test files detected (mcp-servers/eve-ng-mcp-server/tests).Good: Lockfile present (mcp-servers/azure-network-mcp/requirements.txt). Installs are reproducible.Good: Dependency manifest found (mcp-servers/azure-network-mcp/requirements.txt).
- RALPH INPUTS
- scripts
- specs
- src
- testbed
- tests
- ui
- workspace
- .env.example
- .gitignoreGood: .gitignore present.
- AGENTS.md
- blender_addon.py
- CLAUDE.md
- DefenseClawMCPScan.md
- DefenseClawSkillScan.md
- HEARTBEAT.md
- IDENTITY.md
- LICENSEGood: Licensed under Apache-2.0.
- N2N-PEERING-NETCLAWS.md
- netclaw.jpg
- PEERINGEXAMPLE.md
- 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.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.
- SOUL-EXPERTISE.md
- SOUL-SKILLS.md
- SOUL.md
- TOOLS-REFERENCE.md
- TOOLS.md
- USER.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/automateyournetwork/netclaw)