~/shop/qbcore
25 of the 29 scripts in the catalogue run on QBCore. QBCore is where most servers started after 2021, and its exports are close enough to ESX that a well-written script can serve both from one codebase. That is what these do: the framework is detected at boot and every money, job and identifier call goes through the same bridge, so nothing here is a QBCore fork of an ESX script.
Qbox is a QBCore fork and works through the same compatibility layer — if a script says QBCore, it runs on Qbox. Where a script needs qb-target rather than ox_target, it auto-detects whichever is installed rather than requiring one.
Yes. Qbox is a QBCore fork and the exports these scripts call are the ones Qbox kept, so anything marked QBCore runs on it. If something ever diverges it is a bridge-file edit, and the bridge is open on every tier.
qb-multicharacter ships with the framework and is fine for a server that wants a spawn list. Var-MultiChar is for the ones that want the character select to look like a menu rather than a debug screen — the comparison guide puts both side by side with prices.
Neither, specifically. Scripts that use interaction detect ox_target, qb-target or Var-Interact at boot and fall back to a native prompt if none is present, so you keep whatever your server already runs.
Both. Item handling is detected the same way as the target system: ox_inventory when it is there, the framework's own inventory otherwise. The product pages name the exact inventory integrations per script.