repomix-unmixer
Unmix Repomix. Inspect the code, not its side effects.
Security-first, offline unpacking: reconstruct Repomix Markdown, XML and JSON exports into readable file trees—without ever executing recovered code. The extractor rejects unsafe paths, refuses overwrites, enforces resource limits and omits common auto-activating configurations.
Built for safer static inspection of untrusted exports in a trusted local output directory; not a sandbox, malware scanner or guarantee that recovered files are confidential.
Core features
- Three export formats: reconstruct text files and directories from Repomix Markdown, XML and JSON.
- Block unsafe paths: reject traversal, Windows-special names, duplicate/case-colliding paths and file/directory conflicts before writing.
- Protect existing files: dry-run first; fresh-output-only staged writes refuse existing destinations, with file-count and byte limits.
- Reduce accidental auto-execution: exclude common agent/IDE auto-start configuration and environment files; never run recovered code or make network requests.
- CLI, batches and agents:
unmix-repomixfor individual exports,reconstruct-allfor Markdown batches, plus the portable Agent Skill.
Quick start
Requires Python 3.10+. From a trusted checkout (not from a recovered repository):
python3 -m pip install .
One export (Markdown, XML or JSON)
unmix-repomix ./repomix-output.md ./restored-tree --dry-run
unmix-repomix ./repomix-output.md ./restored-tree
# Other supported formats:
unmix-repomix ./repomix-output.xml ./restored-xml
unmix-repomix ./repomix-output.json ./restored-json
The CLI detects the input format automatically. For XML, Repomix --parsable-style is recommended when content is ambiguous. Plain-text and line-numbered exports are unsupported.
Batch Markdown exports
Place your own .md exports inside repomix-files/ (ignored by Git), then:
reconstruct-all --dry-run
reconstruct-all
Batch output appears in reconstructed/. The original export and any reconstructed files remain your responsibility; never commit or publish them without review.
Use it with an AI coding agent
This repository includes a portable Agent Skill. Agent-host integration is not yet verified on every platform (tracked as P1-08).
Agent setup prompt — copy and paste:
Work in this trusted repomix-unmixer repository.
Read AGENTS.md, SECURITY.md, and
skills/repomix-unmixer/SKILL.md.
Set up the Python CLI in an isolated environment from this trusted
checkout, check --version and --help, and run only the included
synthetic extractor tests. If this agent host supports Agent Skills,
register the existing skill using its documented mechanism; otherwise
use the CLI directly. Do not invent host-specific installation steps.
Never execute, import, build, install, test, or run tools from files
reconstructed from a Repomix export. Keep the repository private,
never commit input/output snapshots, and report what you verified
and which host checks remain deferred.
For development tasks, tell the agent to read AGENTS.md and tackle one ID from the backlog, using a branch, tests, commit, push and PR.
How it fits
| Repomix | repomix-unmixer | |
|---|---|---|
| Direction | Repository → packed export | Packed export → file tree |
| Main job | Prepare an aggregated code snapshot | Recreate individual files for inspection |
| Execution | Separate tool | Never runs recovered code |
repomix-unmixer is independent of the Repomix project, not an official Repomix component.
Safety and limitations
Reconstructed content is untrusted and may include secrets. Exclusions are not secret scanning; neither input nor output is automatically safe to share. Avoid opening output in tools that run workspace tasks or auto-load plugins. Use a fresh directory that other users cannot modify.
Parser fixtures were checked against Repomix 1.17.0–1.19.0. Plain-text and line-numbered exports are unsupported; original Git history, omitted binaries and information removed by Repomix cannot be recovered.
Read Security, static inspection, parser compatibility, and exclusion rules before handling untrusted inputs.
Documentation
Docs preview · FAQ · Agent Skill · Contributing · Backlog · Release checklist
Status: private pre-release, MIT-licensed. No PyPI release is claimed. Public release requires completion of the remaining security and provenance checks.
Metadata
Release files for repomix-unmixer 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| repomix_unmixer-0.1.0.tar.gz | 33.3 kB | With provenance | Details for repomix_unmixer-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| repomix_unmixer-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for repomix_unmixer-0.1.0-py3-none-any.whl |
Total release size: 51.6 kB
Release files / repomix_unmixer-0.1.0.tar.gz
| Download URL | repomix_unmixer-0.1.0.tar.gz |
|---|---|
| Size | 33.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ef9b3ea75758013e722b50c521d1741f62194baeb1f48643649a3119edf62d09
|
|
BLAKE2b-256 checksum How to use checksums |
7316c8affce395f0782f20428628ac188bcc5f102f54810673efa398f03d5f47
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.
Transparency logRelease files / repomix_unmixer-0.1.0-py3-none-any.whl
| Download URL | repomix_unmixer-0.1.0-py3-none-any.whl |
|---|---|
| Size | 18.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d2e9b9c45edfe9c1ae8d36a1d2859cb6b1e1b2a63ec14da1491f72c86950804e
|
|
BLAKE2b-256 checksum How to use checksums |
b4357458f34d51d46361e6bb030ad3996e88247d6a57cb235d7a56c24ff30f7c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.
Transparency logSecurity for repomix-unmixer 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for repomix_unmixer-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.