FZX2 is a command-line tool for packaging Python projects into portableDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/WyattBrashear/507ex-utils2/llms.txt
Use this file to discover all available pages before exploring further.
.507ex executables that carry their own metadata, dependency declarations, and integrity hashes. When you run fzx2 build, it zips your project directory, prepends a structured metadata header, and produces a single file you can share, store, or push to a CAR (Central Application Repository) server. Anyone with fzx2 installed can then run that file directly — locally or by pulling it from a CAR URL — without needing to know what packages it requires or how to set up the environment.
507ex 2.0 vs the original format
The original 507ex format was a thin wrapper around a zip archive with no standardized metadata. Version 2.0 (produced by FZX2) replaces that with a well-defined binary header that travels with every executable:| Field | Description |
|---|---|
507ex-hash | BLAKE2s content hash for integrity verification |
507ex-hashmode | Hash algorithm used (always blake2s in 2.0) |
507ex-id | Randomly assigned UUID per build |
507ex-dtoc | Timestamp of when the executable was built |
507ex-depends | Boolean indicating whether a dependfile is present |
fzx2 exec verify the file hasn’t been tampered with before running it, and let tooling inspect executables without executing them.
Key improvements in 2.0
- No AI-generated code. The entire FZX2 toolchain is hand-written, giving you a predictable and auditable build process.
- Enhanced metadata. Every
.507exfile embeds a content hash, build timestamp, UUID, and dependency flag in its header — making executables self-describing. - Automatic dependency management. The
dependfileformat lets you declare pip packages and platform constraints. FZX2 reads and installs them at execution time, so the receiver doesn’t need to manage a virtual environment manually. - CAR server authentication. The built-in push/pull server generates a one-time numeric secret code on upload. The receiver must present the correct code (as a SHA-256 hash) to download the file, preventing unauthorized retrieval.
Key concepts
Executable (.507ex file): The output of fzx2 build. A binary file containing a metadata header followed by the original zip of your project directory.
Runfile: A plain-text file in your project root that contains the shell command used to run your project (e.g., python3 main.py). This is required — fzx2 build will refuse to proceed without it.
Dependfile: An optional plain-text file that declares pip packages your project needs, along with an optional platform constraint. FZX2 reads this at execution time and installs any missing packages before running the executable.
CAR server: A lightweight Flask server bundled with FZX2 (fzx2 start_server). It exposes a /push endpoint for uploading executables and a /pull/<file_id> endpoint for authenticated download. Use fzx2 upload to push a .507ex file, then share the returned URL and secret code with your recipient.
Explore the docs
Installation
Install FZX2 via pip, compiled binary, or from source.
Quickstart
Build and run your first 507ex executable end to end.
CLI reference
Full reference for all FZX2 commands and options.
Format overview
Understand the 507ex 2.0 binary format and header structure.
Runfile
How to write a runfile that tells FZX2 how to start your project.
CAR server
Host and share executables with the built-in CAR server.