0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
An open-source AI assisted firmware analysis tool
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 `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
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 AGPL-3.0.
Engineering
61
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/docs.yml).
Test files detected (backend/tests).
Lockfile present (backend/uv.lock). Installs are reproducible.
Linter or formatter configured (frontend/eslint.config.js).
Project health
100
Dependency manifest found (backend/pyproject.toml).
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)
- 46Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 232Watchers
Responsiveness
- 1d 16hMedian issue response
- 6hMedian PR merge time
- 3Open issues
Repository files21 root entries
- .githubGood: CI is configured (.github/workflows/docs.yml).
- backendGood: Test files detected (backend/tests).Good: Lockfile present (backend/uv.lock). Installs are reproducible.Good: Environment pinned via backend/Dockerfile.Good: Dependency manifest found (backend/pyproject.toml).
- carving
- docs
- emulation
- enterprise
- frontendGood: Linter or formatter configured (frontend/eslint.config.js).
- fuzzing
- ghidra
- harness-build
- images
- scripts
- .env.example
- .gitignoreGood: .gitignore present.
- CLAUDE.md
- docker-compose.yml
- launch.sh
- LICENSEGood: Licensed under AGPL-3.0.
- mkdocs.yml
- 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.
- SECURITY.mdGood: Security policy present.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/digitalandrew/wairz)