Good shape overall. A few tweaks would push it into the top tier.

An open-source AI assisted firmware analysis tool

Documentation

81

Contributing guide5pt0

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.

README12pt90

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under AGPL-3.0.

Engineering

61

Issue and PR templates6pt0

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/CD14pt40

CI is configured (.github/workflows/docs.yml).

Tests18pt80

Test files detected (backend/tests).

Reproducibility6pt80

Lockfile present (backend/uv.lock). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (frontend/eslint.config.js).

Project health

100

Dependency manifest6pt100

Dependency manifest found (backend/pyproject.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 46
    Forks
  • 0
    Releases

Community

  • Community health
  • authors own >50% of commits
  • 232
    Watchers

Responsiveness

  • 1d 16h
    Median issue response
  • 6h
    Median PR merge time
  • 3
    Open issues
Repository files21 root entries
  • .github
    Good: CI is configured (.github/workflows/docs.yml).
  • backend
    Good: 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
  • frontend
    Good: Linter or formatter configured (frontend/eslint.config.js).
  • fuzzing
  • ghidra
  • harness-build
  • images
  • scripts
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • CLAUDE.md
  • docker-compose.yml
  • launch.sh
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • mkdocs.yml
  • README.md
    Good: 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.md
    Good: Security policy present.