PACKAGES / ONE CONTRACT PER RUNTIME

Install the packing engine where your code already runs.

Every component of the suite is versioned and released together; the Go, Java and .NET ports follow on their own version line. Identity, install command, licence and runtime requirement come from the package manifests, not from this page.

PACKAGE CONTRACT

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. The Go, Java and .NET packages are a different thing and are labelled as one: ports of the reference engine, each held to byte-identical results on the conformance corpus of the version it implements.

MINIMAL REQUEST
{
  "items": [
    { "id": "box", "quantity": 8,
      "dimensions": { "length": "50", "width": "50", "height": "50" } }
  ],
  "containers": [
    { "id": "carton",
      "inner_dimensions": { "length": "100", "width": "100", "height": "100" } }
  ]
}
PACKAGE MAP
PACKVIUM CONTRACTPython engineENGINEPHP engineENGINERust coreENGINENode enginenative N-API addonJavaScript fallbackPython native adapterBINDINGBrowser enginePORTS OF THE REFERENCE ENGINE, ON THEIR OWN VERSION LINEGo portPORT · 1.3.0Java portPORT · 1.3.0.NET portPORT · 1.3.0byte-identicalcompiled to WASMRust-backedfalls back to
ENGINEBINDINGPORT

Packages shown: 9

ENGINE · PyPI

Python engine

Reference engine: the full solver portfolio and all five extension points, with zero runtime dependencies. Byte-identical to PHP on every fixture.

pip install packvium
Version 1.11.0Requires Python >= 3.9License MITFixtures 3Registry packvium
ENGINE · Packagist

PHP engine

Second reference engine: the same solver portfolio and extension points as Python, byte-identical on every fixture.

composer require packvium/packvium
Version 1.11.0Requires PHP >= 7.3License MITFixtures 2Registry packvium/packvium
ENGINE · npm

Node engine

Native N-API addon when one is built, and a deterministic JavaScript fallback when it is not — the same request either way.

npm install @packvium/engine
Version 1.11.0Requires Node >= 16License MITFixtures 2Registry @packvium/engine
BINDING · npm

Browser engine

The Rust core compiled to WebAssembly, so packing runs in the page without a round trip. Same conformance fixtures as the other engines.

npm install @packvium/browser
Version 1.11.0Requires WebAssembly-capable browserLicense MITFixtures 1Registry @packvium/browser
BINDING · PyPI

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.

pip install 'packvium-native[native]' packvium
Version 1.11.0Requires Python >= 3.9License MITFixtures 1Registry packvium-native
ENGINE · crates.io

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.

cargo add packvium
Version 1.11.0Requires Rust >= 1.88License MITFixtures 1Registry packvium
PORT · Go modules

Go port

The reference engine reimplemented in Go, standard library only, and byte-identical to the reference on the 1.3.0 conformance corpus.

go get github.com/packvium/packvium-go
Version 1.3.0Requires Go >= 1.13License MITFixtures 1Registry github.com/packvium/packvium-go
PORT · Maven Central

Java port

The reference engine ported to Java with no runtime dependencies, and byte-identical to the reference on the 1.3.0 conformance corpus.

implementation("com.packvium:packvium:1.3.0")
Version 1.3.0Requires Java >= 17License MITFixtures 1Registry com.packvium:packvium
PORT · NuGet

.NET port

The reference engine reimplemented in C# with no runtime dependencies, held to the 1.3.0 conformance corpus, as the Go and Java ports are.

dotnet add package Packvium
Version 1.3.0Requires .NET >= 8License MITFixtures 1Registry Packvium
CHOOSING ONE

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; a Go, Java or .NET service installs the port, which speaks the 1.3 contract.

01role

Engine, binding, port, or workspace tool

02registry

Where the package is published

03install

The exact install command

04requires

Minimum runtime version

05license

MIT across the whole family

06repository

Canonical public source

07fixtures

Committed cases it is exercised against

08published

Available today, or built but not yet released