Getting some notice. Tests and CI would be the fastest wins.
Experimental AI Agent Driven Decomp of Star Fox Adventures.
Documentation
82
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 CC0-1.0.
Engineering
26
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
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/build.yml).
Linter or formatter configured (.flake8).
Project health
68
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
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)
- 1Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 18Watchers
Responsiveness
- 4d 4hMedian issue response
- <1hMedian PR merge time
- 0Open issues
Repository files21 root entries
- .claude
- .githubGood: CI is configured (.github/workflows/build.yml).
- .vscode
- assets
- config
- docs
- include
- orig
- resources
- src
- tools
- .flake8Good: Linter or formatter configured (.flake8).
- .gitattributes
- .gitignoreGood: .gitignore present.
- agentic_loop.py
- AGENTS.md
- CLAUDE.md
- configure.py
- LICENSEGood: Licensed under CC0-1.0.
- 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.
- tools_local_decode.py