~/shop/qbox
25 of the 29 scripts in the catalogue run on Qbox. Qbox is a maintained fork of QBCore, and the exports these scripts call are the ones it kept. So there is no Qbox build to download: every script listed as QBCore runs on Qbox through the same bridge, and the bridge file ships open even on the Escrow tier if your setup ever needs a line changed.
Qbox leans harder on ox_lib and ox_inventory than mainline QBCore does. Everything here detects both rather than requiring either, so a modern Qbox stack and a conservative QBCore one run the same script unmodified.
There is no separate build, and that is deliberate. Qbox kept the QBCore exports these scripts call, so the QBCore path serves it. A separate fork would only mean two codebases drifting apart.
They detect them. ox_inventory is supported out of the box wherever items are involved, ox_lib is used when present and never required. That suits Qbox, where both are usually already installed.
The framework bridge is an open file on every tier, so a renamed export is a one-line fix on your side rather than a wait. Report it and it lands in the next update for everyone, which is lifetime and free.