Live2D Bundle Preflight

Catch broken Live2D package references before delivery

Live2D Bundle Preflight is an offline command-line checker for a supported Live2D delivery ZIP. It catches missing files, broken literal references, path case mismatches, duplicate entries, unsafe archive paths, and selected .model3.json structure problems before handoff.

The tool reads the ZIP directly. It does not extract or execute its contents.

Check one delivery

./live2d-preflight check --input complete-delivery.zip --json report.json

Exit code 0 means PASS, 1 means BLOCKED, and 2 means the input could not be checked. The canonical JSON report can be stored with a delivery, attached to a CI job, or reviewed before handoff.

Check a batch

./live2d-preflight check-many --input model-a.zip --input model-b.zip --json batch-report.json

Batch inputs are ordered deterministically by basename and must use unique basenames.

What this release checks

• ZIP readability, path safety, symlinks, duplicates and collisions;
• archive limits and exactly one case-sensitive .model3.json;
• integer model setting Version 3;
• literal references to .moc3, textures, expressions and motions;
• optional physics, pose, user data, display info and motion sound references;
• exact path case and existing non-directory targets;
• supported Groups and HitAreas structure;
• packaging debris as non-blocking warnings.

Included

• one static Linux binary for the architecture named by the download;
• four synthetic pass, blocked and error fixtures;
• quick-start README, supported-input contract and support boundary;
• perpetual buyer license and complete Go toolchain notices;
• no account, activation, telemetry, subscription or network requirement.

Choose linux-amd64 for 64-bit Intel or AMD Linux and linux-arm64 for 64-bit ARM Linux. Both packages were exercised on Linux in the release process. That evidence does not guarantee every distribution or environment.

Intentionally narrow

This version does not interpret .moc3, render the model, judge artwork or rig quality, or validate tracking or visual physics behavior. It does not repair a package or guarantee compatibility with a viewer or streaming application. It supports exactly one Version 3 model setting per ZIP and checks referenced files by literal package path; it does not validate the bodies of PNG, WAV, .moc3, or optional JSON files. Windows and macOS builds are not included.

Frequently asked questions

What does it check?

It checks a supported delivery ZIP for archive safety, exactly one Version 3 .model3.json, literal references to required and optional files, path case, duplicates, collisions, and selected Groups and HitAreas structure.

Does PASS guarantee that the model works everywhere?

No. PASS means no issue covered by this release was found. It does not prove rendering, artwork quality, rig quality, tracking behavior, visual physics, performance, or compatibility with every application and Linux distribution.

Does it open or interpret the .moc3 file?

No. It checks that the referenced .moc3 path exists as a non-directory ZIP entry. It does not decode, interpret, execute, or validate the file body.

Will it repair my package?

No. Reports identify covered findings so that you can correct the source package. The tool does not rename, rewrite, generate, or repair files.

Will it extract or execute my ZIP?

No. The archive is inspected directly and its contents are not executed.

Can I use it in CI?

Yes. Exit code 0 means PASS, 1 means BLOCKED, and 2 means an input or execution error. JSON reports are canonical for the same effective input.

Which download should I choose?

Use linux-amd64 on 64-bit Intel or AMD Linux and linux-arm64 on 64-bit ARM Linux. No Windows or macOS binary is included.

Does it need internet access, an account, or activation?

No. The binary runs offline and requires no account, activation, telemetry, subscription, or network connection.

What should I include in a support request?

Include the version, architecture, exact command, exit code, JSON report, and the smallest synthetic or redacted fixture that reproduces the issue. Do not post a proprietary model or customer delivery publicly.

AI disclosure and trademarks

AI assistance was used during development, testing, documentation, page preparation, and generated media. The shipped executable contains no model, generative feature, remote AI service, telemetry, or runtime AI dependency.

Live2D and Cubism are trademarks of their respective owners. This product is not affiliated with, approved, sponsored, or endorsed by Live2D Inc.