Pagonic is an alpha Python ZIP toolkit focused on safe archive inspection, secure extraction, and repeatable local benchmarking. Its main idea is simple:
Inspect before you extract.
- A core library for inspecting, writing, reading, and validating ZIP archives.
- A
pagoniccommand-line interface for inspect, verify, safe extract, and ZIP utilities. - An optional PyQt6 GUI launched with
pagonic-gui.
This repository is currently prepared as an alpha-stage, test-backed public release. The import package remains Pagonic for compatibility; the distribution name is pagonic. No PyPI or TestPyPI package is published for this release; install from a local checkout.
Pagonic started more than a year ago as one of my earliest software-learning projects. Its first direction was much broader and more experimental: a ZIP/archive engine with compression, extraction, GUI ideas, benchmarking, and performance experiments.
After many iterations, I revised the project direction and narrowed the public scope into something clearer:
Pagonic is not trying to be another desktop archive manager. It is becoming a security-aware ZIP inspection and safe extraction toolkit.
This v0.4.0 release builds on the first cleaned-up public direction. It keeps
the useful ZIP core, CLI, tests, and safety work while making the focused reader,
writer, inspection, and contribution surfaces clearer for the next stage of
development.
Pagonic is still evolving, but its purpose is now clearer: inspect first, extract safely.
No PyPI or TestPyPI package is published for this release, so install from a local checkout after cloning the repository.
For CLI-only use from a local checkout:
python -m pip install .For local development:
python -m pip install -e .[dev,gui]For CLI-only development with test dependencies:
python -m pip install -e .[dev]Experimental performance helpers are optional and are not required by inspection or safe extraction:
python -m pip install -e .[performance]The GUI is optional. If PyQt6 is not installed, pagonic-gui exits with a clear install message.
pagonic --help
pagonic inspect suspicious.zip
pagonic inspect suspicious.zip --json
pagonic inspect suspicious.zip --markdown
pagonic verify release.zip
pagonic verify release.zip --max-risk medium
pagonic safe-extract upload.zip output/
pagonic safe-extract upload.zip output/ --dry-run
pagonic list archive.zip --tree
pagonic compress path/to/file.txt -o archive.zip
pagonic config listUse inspect before extraction for untrusted ZIP files. safe-extract applies
the inspection gate before writing files, supports --dry-run, and refuses ZIP
entries that use unsupported compression methods.
from Pagonic.core.formats.zip_writer import ZipWriter
from Pagonic.core.formats.zip_reader import ZipReader
writer = ZipWriter("archive.zip", compression_level=6)
writer.add_file("file.txt")
writer.finalize()
reader = ZipReader("archive.zip")
report = reader.inspect()
if report.risk_level in {"ok", "low"}:
reader.extract_all("output")Pagonic/ Python package
tests/ pytest suite
docs/ public documentation
examples/ small runnable examples
pyproject.toml package metadata and tool config
- Architecture
- User Guide
- Developer Guide
- 0.4 Migration Notes
- Roadmap
- Changelog
- Contributing
- Security Policy
- Code of Conduct
Focused contributions are welcome, especially improvements to inspection determinism, security regression coverage, safe extraction policy, CI integration, and documentation. Read CONTRIBUTING.md, check the 0.5 roadmap, and use the issue templates before opening a pull request. Do not include private plans, local paths, secrets, generated archives, or benchmark output in public changes.
Inspection reports are deterministic and do not use runtime AI. Current risk flags include:
| Flag | Severity | Meaning |
|---|---|---|
path_traversal |
high |
Entry contains .. path segments. |
absolute_path |
high |
Entry uses a POSIX absolute path. |
windows_drive_path |
high |
Entry looks like a Windows drive path. |
hidden_file |
low |
Entry basename starts with .. |
empty_filename |
medium |
Entry cannot be mapped to a useful safe path. |
too_many_files |
high |
Archive exceeds the configured file-count limit. |
large_uncompressed_size |
high |
Archive exceeds the configured uncompressed-size limit. |
high_compression_ratio |
high |
Entry expands much more than its compressed size. |
unsupported_compression_method |
medium |
Entry uses a ZIP method Pagonic does not currently support; safe-extract refuses it. |
crc_or_structure_error |
critical |
ZIP structure or CRC validation failed. |
suspicious_extension |
medium |
Entry has an executable or script-like extension. |
duplicate_filename |
high |
The same archive filename appears more than once. |
normalized_path_collision |
high |
Different names resolve to the same sanitized path. |
case_insensitive_collision |
high |
Names collide on case-insensitive filesystems. |
unicode_normalization_collision |
high |
Different Unicode spellings normalize to one path. |
symlink_entry |
high |
ZIP metadata marks the entry as a symbolic link. |
encrypted_entry |
high |
Entry contents cannot be validated by the current workflow. |
nested_archive |
low |
Entry appears to contain another archive; it is not recursively inspected. |
long_filename |
medium |
Entry name exceeds the configured review length. |
long_archive_comment |
low |
Archive comment exceeds the configured review length. |
pagonic inspect --json emits a stable alpha report with archive totals,
overall risk_level, top-level risk_flags, recommended_action, and per-entry
metadata. pagonic inspect --markdown renders the same inspection as a saved
human-readable report.
Use inspect before extraction when the archive is untrusted. For automation,
verify returns exit code 0 only when the report is within --max-risk and
has no validation errors. safe-extract applies the same inspection gate before
writing files and supports --dry-run.
The older extract command remains as a compatibility command for trusted
archives. It uses secure path handling, but it is not an inspection policy gate;
use safe-extract for untrusted input. list and info are read-only display
commands and do not replace an inspection report.
The current public release is 0.4.0: an alpha-stage, test-backed release with
security-aware ZIP inspection, gated safe extraction, core ZIP behavior, CLI
support, optional GUI packaging, MIT license, and CI-ready tests.
Pagonic is not intended for production-critical automation yet and is not positioned as a general multi-format desktop archive manager. The next work is the proposed 0.5 milestone: stabilizing report and policy contracts, expanding the synthetic security regression corpus, improving CI integration examples, and making public contribution safer and clearer.