Install the engine where your code already runs.
Every component of the suite is versioned and released together. Identity, install command, licence and runtime requirement come from the package manifests, not from this page.
Every package answers the same request document.
Engines are independent implementations rather than ports, and the conformance suite holds them to one schema and one corpus. Python and PHP are held to byte-identical canonical results; the Rust core and the JavaScript fallback are held to independent validity and a per-fixture objective floor.
{
"items": [
{ "id": "box", "quantity": 8,
"dimensions": { "length": "50", "width": "50", "height": "50" } }
],
"containers": [
{ "id": "carton",
"inner_dimensions": { "length": "100", "width": "100", "height": "100" } }
]
}Python engine
Reference engine: the full solver portfolio and all five extension points, with zero runtime dependencies.
PHP engine
Second reference engine, held to byte-identical canonical results against Python on every fixture.
Node engine
Native N-API addon when one is built, and a deterministic JavaScript fallback when it is not — the same request either way.
Browser engine
The Rust core compiled to WebAssembly, so a packing answer can be computed in the page without a round trip.
Python native adapter
Rust-backed adapter for Python. Uses the native wheel when it is present and the pure Python engine when it is not.
Rust core
The independent Rust packing core and its stable C ABI. Its own solver portfolio, held to independent validity and a per-fixture objective floor.
Workspace manager
Add-only overlay installs, SHA-256 admission control and the release gate. Not a packing engine.
The runtime is a deployment decision.
Pick the package that matches your stack. If you need the answer in a browser without a round trip, that is the WebAssembly build; if you need it inside an existing Python or PHP service, those are the reference engines.
roleEngine, binding, or workspace tool
registryWhere the package is published
installThe exact install command
requiresMinimum runtime version
licenseMIT across the whole family
repositoryCanonical public source
fixturesCommitted cases it is exercised against
publishedAvailable today, or built but not yet released