sm64ds-decomp
Demonstrates reverse-engineering methodologies and matching decompilation techniques applicable to legacy codebase modernization, binary analysis, and unders…
From-scratch, byte-matching decompilation of Super Mario 64 DS (sm64ds decomp) into C, with a live progress atlas and matching tools.
- Generate C source code from Super Mario 64 DS binary sections using matching tools.
- Find decompiled function signatures and memory layouts across the entire game codebase.
- Automate byte-level verification of reverse-engineered code against original ROM data.
Demonstrates reverse-engineering methodologies and matching decompilation techniques applicable to legacy codebase modernization, binary analysis, and understanding closed-source system internals—critical skills for teams maintaining or integrating with undocumented software.
Engineering teams tasked with legacy code recovery, binary analysis, or reverse-engineering closed-source dependencies.
https://github.com/tangosdev/sm64ds-decomp
By tangosdev
How to Get It
claude plugins install tangosdev/sm64ds-decomp
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me generate C source code from Super Mario 64 DS binary sections using matching tools
Trust Signals Auto-scanned
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 116 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 116 GitHub stars; contributors unknown; last commit 0d ago; license MIT.