Open the resource workspace
Install the Windows desktop app from its product page and open the resource folder you want to inspect. Keep a version-control checkpoint or backup before accepting changes.
Index reads fxmanifest.lua and legacy __resource.lua files. Start there to check scripts, dependencies, files, data_file declarations, and the NUI page.
Inspect the findings
Run Sentinel to review manifest paths, asset hygiene, secrets, and release risks. Open a finding to read its evidence and rule identifier before deciding how to address it.
Use Probe to analyse supported Lua, JavaScript, and TypeScript. Wire shows relationships between functions, events, exports, commands, and NUI callbacks. These tools inspect source without executing the resource; they cannot prove its runtime behaviour.
Review each proposed write
Changes are staged as a plan for review. Check the affected files and proposed result before approving a write. A warning may be intentional, so use a documented project suppression when appropriate instead of applying every suggestion.
For vehicle metadata, Chassis handles metadata bundles and Align checks linked model names, siren IDs, light IDs, and modkits. Review the relationships together after a rename.
Build and test the archive
Use Bundle to create the resource ZIP. Resolve the release-validation findings and inspect the output contents before distributing it. Development files and credentials should not travel with the package.
Extract the finished archive into a separate test server resource folder and check startup and the actual player flow. Passing static checks is not a substitute for a FiveM session.