Skip to main content

Documentation 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.

The unpack command extracts the contents of a .507ex file into a directory under 507ex-unpacked/ in your current working directory. It is designed for inspecting what a package contains — reading the runfile, reviewing bundled scripts, or auditing a .507ex file before execution — without running any code.

​
Usage

fzx2 unpack <path>
​
path
string
required
Path to the .507ex file to unpack. This value is used both as the source file passed to zipfile.ZipFile and as the name of the subdirectory created inside 507ex-unpacked/. See the note below on path and directory naming.

​
How it works

1

Create the output root

If 507ex-unpacked/ does not already exist in the current working directory, it is created.
2

Create a subdirectory named after the path argument

A subdirectory named exactly after the <path> argument is created inside 507ex-unpacked/. For example, fzx2 unpack my_app.507ex creates 507ex-unpacked/my_app.507ex/.
3

Extract the ZIP payload

The .507ex file (which is a valid ZIP archive, optionally with the FZX2 metadata header prepended) is opened with zipfile.ZipFile and all its contents are extracted into the subdirectory.

​
Example

fzx2 unpack my_app.507ex
After running this command from /home/user/projects/: 
507ex-unpacked/
└── my_app.507ex/
    ├── runfile
    ├── dependfile
    └── main.py
You can then read the runfile to see what command the executable would run: 
cat 507ex-unpacked/my_app.507ex/runfile

​
Naming behavior

The <path> argument is used verbatim as the subdirectory name inside 507ex-unpacked/. Passing a bare filename like my_app.507ex creates 507ex-unpacked/my_app.507ex/. Passing a path with directory components (e.g., builds/my_app.507ex) would attempt to create 507ex-unpacked/builds/my_app.507ex/ — ensure the intermediate directory exists first, or pass only the filename.
unpack does not verify the BLAKE2s hash or parse the FZX2 metadata header. It simply opens the file as a ZIP archive. If you want hash verification, use fzx2 exec instead.
Use unpack to review a .507ex file’s runfile and bundled scripts before trusting it enough to execute with fzx2 exec.

Build docs developers (and LLMs) love

Get started for freeTalk to us