Compatibility Analyzer
Review manifests, dependencies and framework API references locally.
Resource text files → dependency graph and JSON diagnosticsInputs
Select a resource folder or add text files with relative paths. Files stay in this tab and are never executed.
Limit: 100 files, 256 KiB each, 2 MiB total. Review one resource and its dependencies at a time.
0 files selected
Results
Add files and run analysis to inspect dependencies, start order and literal API references. No result certifies runtime compatibility.
How to review a resource
Select a folder containing resource subfolders, or paste files using paths such as
my-job/fxmanifest.lua and my-job/server.lua. Include dependency manifests and provider Lua
files to check literal export and event declarations. Add server.cfg to compare explicit starts.
Selecting another folder replaces the current selection. No ZIP extraction or code execution occurs.
The report shows declared dependencies and @resource/file.lua imports, missing selected files,
dependency cycles, duplicate starts, suspicious explicit start order, legacy core retrieval and
QBCore/Qbox API references. Findings include file/line locations, severity, suggested next actions,
and links to relevant documentation. Warnings are displayed before informational observations.
Copy or download JSON for a human-readable report, or export SARIF 2.1.0 for a code-review tool. Both formats contain paths and findings but exclude source text and configuration values. Neither format verifies runtime compatibility or automatically patches your code. Analytics receives only the tool name and action, never files or findings.
Static evidence and runtime testing
An absent export or dependency means it was not found in the selected text. It may exist in files
you did not select, a generated declaration or a different fork. Lua functions, concatenations,
globs, exec files and category starts require manual review. API argument types, client/server
context, permissions, SQL and actual behavior remain unverified. Qbox bridge usage is a migration
review item, not a guaranteed failure.
Compare the result with the resource compatibility checklist, core object guide, QBCore/Qbox comparison and config validator. Start and restart the exact resource commits on an isolated FXServer and database before changing a production server.