DEVELOPERS // LOCAL TOOL
Find the break
before it ships.
Inspect a project folder in your browser and get file-level findings, likely causes, and practical next steps. Your files stay on your device.
LOCAL PROJECT SCAN
Give the code a second pair of eyes.
Choose a folder or its files. The validator detects the project shape, applies relevant checks, and ignores rules that do not belong to it.
No project loaded yet. Nothing leaves this browser.
ACTIONABLE FINDINGS
Project report
FILE MAP
Project contents.
DEPENDENCY MAP
What connects to what.
Local imports, manifest references, and UI assets are shown here so broken links are easier to trace.
BASELINE COMPARISON
What changed.
WHAT IT CHECKS
Useful by design.
Manifests, package files, source folders, assets, migrations, and expected entry points.
Missing local files, broken relative imports, missing NUI assets, and unresolved FiveM manifest entries.
Secrets, private keys, suspicious paths, oversized files, and accidental publish risks.
Open any finding to see the exact source line and nearby context. Confidence and ignore controls help separate real problems from intentional exceptions.
For repeatable scans, add a .gankbyte-validator.json file to the project. It can choose the project type, ignore folders, and suppress known finding IDs without uploading anything.
{
"type": "fivem",
"ignore": ["vendor/**", "tests/fixtures/**"],
"ignoreFindings": []
}