This release is a pre-release and may not be stable for production use.
regipy-rs
Rust-accelerated core parser for regipy, the OS-independent Python library for parsing offline Windows registry hives (REGF format).
Status: alpha. The Rust backend is validated 1:1 against the pure-Python parser over regipy's full test-hive corpus (every key, every value), but the API and packaging may still change.
What it is
regipy_rs is a PyO3 native extension implementing the performance-critical
parts of registry parsing: hive loading, key navigation, recursive traversal
and value decoding. It is not meant to be used directly — install it alongside
regipy and use the drop-in wrapper:
pip install regipy[rust]
from regipy.registry_rs import RegistryHive # instead of regipy.registry
reg = RegistryHive("/path/to/NTUSER.DAT")
key = reg.get_key(r"\Software\Microsoft\Windows\CurrentVersion\Run")
for value in key.iter_values(as_json=True):
print(value.name, value.value)
for entry in reg.recurse_subkeys(as_json=True):
...
The wrapper exposes the exact same API and dataclasses as
regipy.registry.RegistryHive, so existing code and all regipy plugins work
unchanged.
Parity guarantees
Output semantics intentionally match the Python parser, including its quirks
(string trimming behavior, decode order of try_decode_binary, generator
error semantics on corrupted hives). Parity is enforced by
regipy_tests/comparison_test.py, which traverses every test hive with both
backends and compares every key path, timestamp, value name, type and content.
Building from source
pip install maturin
cd regipy-rs
maturin build --release
pip install target/wheels/regipy_rs-*.whl
Benchmarks
BENCHMARKS.md contains the full report: per-hive timings, cProfile
breakdowns of both backends, SHA-256 parity digests over the complete
traversal output, and a disclaimer documenting intentional divergences.
The entire report is regenerated from source by:
python regipy-rs/benchmark.py --runs 3
See the Reproducing this report section of BENCHMARKS.md for
prerequisites and caveats.
1 maintainer
Metadata
1 maintainer
Release files for regipy-rs 0.1.0a3
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 | |
|---|---|---|---|---|
| regipy_rs-0.1.0a3.tar.gz | 37.2 kB | With provenance | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| regipy_rs-0.1.0a3-cp39-abi3-win_amd64.whl | CPython 3.9 | abi3 | Windows x86-64 | Details |
| regipy_rs-0.1.0a3-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.9 | abi3 | Linux glibc 2.17+ x86-64 | Details |
| regipy_rs-0.1.0a3-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | CPython 3.9 | abi3 | Linux glibc 2.17+ ARM64 | Details |
| regipy_rs-0.1.0a3-cp39-abi3-macosx_11_0_arm64.whl | CPython 3.9 | abi3 | macOS 11.0+ ARM64 | Details |
Total release size: 1.1 MB
Release files / regipy_rs-0.1.0a3.tar.gz
| Download URL | regipy_rs-0.1.0a3.tar.gz |
|---|---|
| Size | 37.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2928826267f8e47d493bd7a5ce72c082686d1d5b5a920a8989e7759425f06dab
|
|
BLAKE2b-256 checksum How to use checksums |
4652e35e53bea59d420ef7d3e32045a3386fbc2487483169f55490bf47512a48
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 13, 2026.
Transparency logRelease files / regipy_rs-0.1.0a3-cp39-abi3-win_amd64.whl
| Download URL | regipy_rs-0.1.0a3-cp39-abi3-win_amd64.whl |
|---|---|
| Size | 192.7 kB |
| Tags | CPython 3.9 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
43f34a33dee08484e90dc122c69a962169a233e0c085913f86bef67ccf691519
|
|
BLAKE2b-256 checksum How to use checksums |
6734ac82692409766d31df79a2ef00f32eadb0bc0b65744703272caecb734393
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 13, 2026.
Transparency logRelease files / regipy_rs-0.1.0a3-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | regipy_rs-0.1.0a3-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 298.9 kB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
760366e5ca9c6bbabbf2c7b1588e7b69f89f4247f50dbe36958f859e56409cc5
|
|
BLAKE2b-256 checksum How to use checksums |
46cdbc184be9c1b65d2f6d945bd6c563825977fec684f643eb7f37c676246a91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 13, 2026.
Transparency logRelease files / regipy_rs-0.1.0a3-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | regipy_rs-0.1.0a3-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 298.6 kB |
| Tags | CPython 3.9 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
175f2813a56b00636f96acbf2c8db75101f2498f0fbd8b2329234e9c6538f91b
|
|
BLAKE2b-256 checksum How to use checksums |
951c76a734dde75d02288ccf6167a0a2dbfee6856cf49be63f19a4839d27f61b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 13, 2026.
Transparency logRelease files / regipy_rs-0.1.0a3-cp39-abi3-macosx_11_0_arm64.whl
| Download URL | regipy_rs-0.1.0a3-cp39-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 280.1 kB |
| Tags | CPython 3.9 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
a733da124062effdc915c3914efcaefba1dc8c4e674c03b90325f380e08e39c6
|
|
BLAKE2b-256 checksum How to use checksums |
82dd11e10a9befa48d99587afed145740e6db5af3304ba2867e4a2288320b64b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 13, 2026.
Transparency logSecurity for regipy-rs 0.1.0a3
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
All 5 files in this release have been uploaded with provenance metadata.
Attestation for regipy_rs-0.1.0a3.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 Oct 13, 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.
