pywimparser
pywimparser is a Python library for reading Microsoft WIM archives.
It focuses on:
- parsing as much metadata as possible
- listing files/directories inside images
- extracting full images or selected paths
This project is read-only for WIM operations. It does not create or modify WIM files.
Backend Model
pywimparser has two runtime paths:
- Native
libwimbackend (ctypes, raw C API)- full metadata traversal
- robust extraction support
- supports XPRESS, LZX, and LZMS through
libwim
- Pure Python fallback
- parses core WIM structures directly
- can list/extract uncompressed resources
- cannot fully decompress entropy-coded XPRESS/LZX/LZMS resources
Use WimParser.parse_backend to see which backend was used for a parse call.
Features
- Archive-level metadata
- header fields (signature, version, flags, chunk size, GUID, parts, image count)
- lookup/offset table entries
- XML document (when available)
- Image metadata
- name, description, display name/description
- file/dir counts and total bytes (when present)
- selected Windows metadata from XML (when present)
- Filesystem metadata
- path, type, timestamps, attributes, size, packed size, stream hash
- Extraction
extract_all()for an imageextract([...])for selected paths
Platform Support
- Packaging:
pywimparseris distributed as a pure-Python wheel (py3-none-any) plus sdist.- The same wheel is installable on Linux/macOS/Windows for Intel and ARM.
- CI coverage:
- Linux: x64 + arm64
- macOS: Intel + Apple Silicon
- Windows: x64 + arm64
- Native
libwimbackend CI:- validated on Linux x64 + arm64
- other platforms use the pure-Python fallback unless
libwimis installed and discoverable
Installation
From PyPI:
pip install pywimparser
For full extraction/compression support, ensure libwim is installed and discoverable.
Build libwim Without ntfs-3g
The repository includes scripts/build_libwim.sh to build shared libwim with:
--without-ntfs-3g--without-fuse--enable-shared--disable-static
This keeps usage in the libwim dual-license path that allows LGPL option when ntfs-3g is not linked.
./scripts/build_libwim.sh
After build, point pywimparser to the library:
export PYWIMPARSER_WIMLIB_PREFIX="$(pwd)/.vendor/wimlib"
# or provide the platform-specific .so, .dylib, or .dll path:
export PYWIMPARSER_LIBWIM="$(pwd)/.vendor/wimlib/lib/libwim.so"
Quick Start
from pywimparser import WimParser
parser = WimParser("install.wim")
metadata = parser.parse()
print(parser.parse_backend) # "libwim-c" or "python"
print(parser.native_backend_available) # True if libwim is usable
print(metadata.header.compression_format)
entries = parser.list_entries(image_index=1)
print(entries[0].path)
parser.extract_all("./out", image_index=1)
parser.extract(["Windows/System32/notepad.exe"], "./out", image_index=1)
CLI
pywimparser info install.wim
pywimparser list install.wim --image 1
pywimparser extract install.wim ./out --image 1
pywimparser extract install.wim ./out --image 1 --path Windows/System32/cmd.exe
Development
Create and activate a virtual environment:
python3 -m venv .venv
source .venv/bin/activate
Install package + dev tooling:
python -m pip install --upgrade pip
python -m pip install -e ".[dev]"
Run the complete local quality suite:
ruff check .
ruff format --check .
python -m coverage run -m pytest -q
python -m coverage report
python -m bandit -c pyproject.toml -r src
python -m pip_audit
python -m fuzz.run_smoke --iterations 10000
Coverage is branch-aware and enforced at 90% for the portable Python
implementation. The native binding is validated in dedicated libwim CI jobs.
Fixture notes are in tests/fixtures/README.md; the full workflow is in
CONTRIBUTING.md, and the latest review evidence is in
AUDIT.md.
For coverage-guided Linux fuzzing:
python -m pip install -e ".[fuzz]"
python -m fuzz.fuzz_parser --seed-corpus tests/fixtures -atheris_runs=20000 -max_len=8192
Build Artifacts
Build wheel + sdist:
python -m build
Releases
Release notes are maintained in CHANGELOG.md. The project uses
Semantic Versioning; while the major version is zero, minor releases may include
intentional compatibility changes and patch releases remain backward-compatible.
Release tags use vMAJOR.MINOR.PATCH and must match the version in
pyproject.toml.
GitHub Actions / PyPI Readiness
The repository includes workflows for:
- linting and formatting checks
- branch-aware tests and coverage enforcement
- Bandit static analysis and dependency vulnerability auditing
- portable mutation fuzzing and Linux Atheris coverage-guided fuzzing
- Python/platform matrices and native libwim integration tests
- wheel/sdist construction and package validation
- Publish (build sdist/wheel, publish with trusted publishing)
Tagged releases verify that the tag matches the package version, validate the wheel and sdist, and publish through PyPI trusted publishing.
Public API
Main class:
WimParser(path)
Methods:
parse(force_reload=False)list_entries(image_index=1)extract_all(destination, image_index=1)extract(paths, destination, image_index=1)
Properties:
parse_backendnative_backend_availablerust_backend_available(compatibility alias)extraction_available
Passing an empty list to extract() is an error; use extract_all() when full
archive extraction is intended.
Security
Treat WIM archives as untrusted data. The pure-Python path validates archive
paths before writing, rejects pre-existing symlink hops, verifies WIM resource
hashes, and parses embedded XML with defusedxml. WIM SHA-1 identifiers are not
proof of authenticity, the pure-Python parser reads the archive into memory, and
native operation depends on the libwim library selected by the environment.
Extract hostile archives with least privilege and application-level size/time
limits. See SECURITY.md for the threat model and private
reporting process.
License
pywimparser is licensed under MIT.
libwim is third-party software with its own license terms. See THIRD_PARTY_NOTICES.md.
This README is technical guidance, not legal advice.
Metadata
Release files for pywimparser 0.2.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 |
|---|---|---|---|---|
| pywimparser-0.2.0.tar.gz | 46.9 kB | With provenance | Details for pywimparser-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pywimparser-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for pywimparser-0.2.0-py3-none-any.whl |
Total release size: 71.2 kB
Release files / pywimparser-0.2.0.tar.gz
| Download URL | pywimparser-0.2.0.tar.gz |
|---|---|
| Size | 46.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b1a8a89475f4276fc684148bd165f69d47921de4a6461a83743f435183e7bc25
|
|
BLAKE2b-256 checksum How to use checksums |
e43821908d0676f5ae8956c049bde678159f71db5364dbe3228c4b1692e44a0a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Jul 19, 2026.
Transparency logRelease files / pywimparser-0.2.0-py3-none-any.whl
| Download URL | pywimparser-0.2.0-py3-none-any.whl |
|---|---|
| Size | 24.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b60aef46e5e9d6c09211978a1d5682850746b471cfd2a48217c486e80f65456a
|
|
BLAKE2b-256 checksum How to use checksums |
0a66cea617307e0a78db64f522c0dcb64550c5987dbddd21b536f0f6c623acd8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Jul 19, 2026.
Transparency logSecurity for pywimparser 0.2.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 pywimparser-0.2.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 Jul 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.