Approved game libraries.

Games can use only libraries in the host’s bundled, pinned catalog that you have approved. Adding an approval cannot authorize an arbitrary crate or download new code.

Current catalog

byteorder-lite 0.1.0 reads and writes numbers in different byte orders. It is approved by default, with default features disabled and no additional features or dependencies.

The signed lockfile must match the exact version, registry source, dependency graph, and archive checksum:

8f1fe948ff07f4bd06c30984e69f5b4899c516a3ef74f34df92a2df2ab535495

GamePKG supplies its bundled source to the isolated build. The game cannot substitute a package, select a different version, or fetch a dependency from the network.

Choose your approvals

Open Settings → Approved game libraries, change the byteorder-lite checkbox, then choose Save settings. Cancel discards edits. The desktop and CLI share these preferences.

gamepkg allowlist list
gamepkg allowlist remove byteorder-lite
gamepkg allowlist add byteorder-lite

Removing approval blocks verification, installation, builds, and new play sessions for games that depend on that library. It does not interrupt a game already running. Games without dependencies continue to use the same source and runtime restrictions.

What source packages cannot do

Guest packages cannot use build scripts, procedural macros, path or Git dependencies, unapproved transitive dependencies, extra dependency features, or binary includes. Every packaged Rust source file is checked, including unused modules. Unsafe guest code and ambient filesystem, network, and process operations are rejected.

Linux builds use locked, offline Cargo in an isolated process without the user’s home directory or network access. Runtime games receive scoped host operations under Wasmtime. Source scanning is a policy filter; build and runtime isolation enforce additional boundaries.

Adding a library to the catalog

The current release has one catalog entry. An unknown name passed to allowlist add is rejected. A new library requires a host update that reviews and bundles its source, pins its complete dependency graph, and tests its permitted build configuration. A creator cannot expand the catalog through a game manifest.

Approval and signatures do not guarantee harmless code. The host, compilers, and graphics drivers remain trusted components. Review the creator and permissions before installation.