Your first audit

1. Create a workspace. A workspace holds your experiences, your team and their audit history.
2. Add an experience. Give it the name players know it by. Linking the Roblox universe ID is optional.
3. Upload an export: a place saved as .rbxlx, a model as .rbxmx, or a folder of Luau sources such as a Rojo project. See Exporting your place.
4. Read the report. Findings are ranked by severity. Each one explains what was found, why it matters, where it is and how to fix it.
5. Fix in Studio and upload again. shipLua compares the new audit with the previous one: fixed issues are resolved, new ones are flagged, and issues that come back reopen.

Severity and confidence

Severity is the worst realistic outcome if the finding is real: players charged without receiving items or a backdoor is critical; lost progress or exploitable remotes is high; reliability and maintenance issues are medium or low.

Confidence says how sure the rule is. High means the pattern is unambiguous. Medium and low mean the rule follows a heuristic that can be wrong, for example when logic lives in another module the rule cannot follow.

Triage

Mark a finding as acknowledged while you work on it, false positive if the rule is wrong for your code, or accepted risk if you have decided to live with it. Those decisions persist across audits and are recorded in the activity log with who made them.