One archive. One meaning. One verified tree.

Sealr turns an untrusted archive into a verified, reusable tree capability. It chooses one explicit interpretation, verifies every member, and returns an evidence receipt. If verification fails, no tree is published.

Downstream tools consume the VerifiedArchive capability or materialized tree. The original archive can be deleted after admission, so another parser cannot silently give the same bytes a different meaning.

Get started · Documentation · Roadmap · Releases

Try it

Download the native Linux, macOS, or Windows archive from v0.1.0-alpha.15 and verify the release before running it.

# Inspect. View JSON goes to stdout; receipt JSON goes to stderr.
./sealr path/to/archive.zip

# Publish the verified tree into a new destination.
./sealr path/to/archive.zip --dest ./out

ZIP32 is the default. Select ZIP64 explicitly with --format zip64. The destination must be new and its parent must already exist. Exit 0 means verified, 2 means not admitted, and 3 means a failed destination effect.

To build from source, the repository pins Rust 1.98.0:

git clone https://github.com/blisspixel/sealr.git
cd sealr
cargo run --locked -p sealr-cli -- path/to/archive.zip

The getting started guide covers source builds, canonical evidence verification, and a Rust example that deletes the source before evaluating a wheel.

See it work

Inspecting a two-member ZIP verifies both members without writing a destination:

This is a rendered summary of verified CLI output. The full walkthrough includes parent-path rejection, materialization, both themes, and reproduction instructions.

Current status

Alpha.15 adds a practical wheel-content release check, measured retention guidance, and a consistent visual identity. Native CI covers Linux, macOS, and Windows. See the release notes for the measured changes.

Sealr is a development preview for integration and adversarial testing. It has no independent security audit or stable production release. Receipts are unsigned, and admission does not establish that a program is safe to execute. This GitHub-only prerelease does not publish a crate to crates.io.

The implementation and security boundary describes supported formats, the explicit Linux worker, resource limits, and open gaps.

What comes next

Move the wheel-content gate into a separately maintained publisher workflow. The validation project exercises released Deepr, Primr, and Recon wheels and measures explicit retention choices.

That work tests API, acquisition, compatibility, and failure handling before more format breadth. The roadmap and pilot contract define the remaining adoption, lifecycle, stability, and independent-review gates.

Go deeper

• CLI usage and formats
• Rust API and evidence
• Complete Python wheel installation handoff
• Compatibility evidence
• Security policy and threat model
• Contributing and documentation index

Apache-2.0. Native archives include dependency license notices.