pyzarlib
pyzarlib provides Python bindings to the Rust zarlib archive library.
The package exposes high-level create, add, remove, join, undo, commit
encryption/decryption, custom metadata read/update, check, info, list, and
extract operations.
ZIP, 7z, RAR, ISO, TAR, TAR.GZ, TGZ, and GZ paths in create_archive and add_archive are
imported by their internal entry paths. Encrypted ZIP/7z/RAR sources and
ZIP/7z/RAR links are not supported. Multi-volume RAR archives and RAR special
entries are rejected. ISO import reads ISO 9660, preferring Rock Ridge over
Joliet and the primary namespace. ISO links, special entries, and UDF-only
images are not supported. ISO import is limited to 100,000 entries, 16 MiB of
directory metadata, and 64 directory levels. TAR symbolic links are preserved where the host
supports them, hard links are imported as regular files, and TAR special
entries are not supported.
The Python API provides read_custom_metadata and update_custom_metadata
for archive-level custom key/value metadata. The zarc-py CLI does not yet
include a metadata command; with the separate zarc CLI, values can also be
managed this way:
zarc meta backup.zar --set project=example
zarc meta backup.zar
zarc meta backup.zar --remove project
Each update appends a commit without file changes. This is distinct from
per-file permissions and timestamps; see the
zarc guide.
Python compatibility
The package requires Python 3.9 or newer. The CI matrix covers standard CPython 3.9 through 3.15, plus free-threaded CPython 3.14t and 3.15t. The PyO3 extension declares that it does not require the GIL; concurrent-call tests exercise the binding from multiple Python threads. A free-threaded test verifies that importing the extension does not turn the GIL back on.
Compatibility review: the official Python 3.14 and Python 3.15 release notes and porting sections, and the PyO3 free-threading guide.
Build and install
Install Maturin and build/install the package from this directory:
python -m pip install maturin
maturin develop --release
To use mimalloc for allocations made by the Rust extension, enable its optional Cargo feature:
maturin develop --release --features mimalloc
To build a wheel:
maturin build --release
Use maturin build --release --features mimalloc to build a wheel with mimalloc.
For development, install the package with pytest support and run the Python API tests from this directory:
python -m pip install -e ".[test]"
maturin develop
python -m pytest
Python zarc example
The package includes a Python CLI port of the main zarc archive commands.
Install the package to get the zarc-py command, or run the example entry point
from this directory:
zarc-py --help
python examples/zarc.py create backup.zar src/ README.md
zarc-py undo backup.zar 1
zarc-py list backup.zar
zarc-py check backup.zar
zarc-py extract backup.zar --output restored --dry-run
It supports create (c), add (a), remove (r), join (j), undo (u), check
(k), info (i), list (l), and extract (e), including path filters and
file list rules. Undo (u) removes trailing commits but never the first commit.
--password prompts without echo where encryption is supported. Progress bars
and interactive ask extraction policies are omitted because the current Python
binding does not provide an interactive progress callback. The source is in
python/pyzarlib/cli.py; it is an example consumer
of the same public Python API documented below, not a second archive
implementation.
The Python API tests exercise archive operations through pyzarlib; the
pytest suite also runs the complete native zarlib unit-test suite so
Rust-only framing, crypto, and data-model tests are included.
Example
from pathlib import Path
import pyzarlib
created = pyzarlib.create_archive(
"backup.zar",
[Path("src"), Path("Cargo.toml")],
)
print(f"Created with {len(created['warnings'])} warning(s)")
for entry in pyzarlib.list_archive("backup.zar"):
print(entry["path"], entry["type"], entry.get("size", ""))
report = pyzarlib.check_archive("backup.zar")
print(f"Checked {report['commits']} commit(s)")
plan = pyzarlib.extract_archive(
"backup.zar",
"restored",
dry_run=True,
)
print(f"Would extract {len(plan['files'])} file(s)")
contents = pyzarlib.extract_archive_to_memory(
"backup.zar",
size_limit=1024 * 1024,
offset=0,
)
for path, data in contents.items():
print(path, len(data))
Read metadata as a dictionary of Python strings, integers, and floats. Set
and/or remove keys with update_custom_metadata; keys beginning with zar.
are reserved, and updates require an unencrypted archive:
pyzarlib.update_custom_metadata(
"backup.zar",
set={"project": "example", "revision": 3},
)
metadata = pyzarlib.read_custom_metadata("backup.zar")
pyzarlib.update_custom_metadata("backup.zar", remove=["revision"])
Password encryption: AES-256-GCM and ChaCha20-Poly1305
Password-encrypted creation supports independently encrypted headers and data.
The encryption_scope argument accepts "data", "header", or
"header-and-data" (the default). With "data", info_archive and
list_archive can read the logical header without a password, but extracting
data still requires one. info_archive reports each commit's header/data
encryption status and AEAD algorithm.
Listing and extraction skip commits whose encrypted headers have no supplied password, so their results can be a partial view of the archive. Extraction still fails when a visible commit's data is encrypted and its password is unavailable. An incorrect password fails authentication.
The aead argument accepts "aes-256-gcm" or "chacha20-poly1305" and
defaults to AES-256-GCM. Each commit has its own encryption descriptor. For
operations over multiple commits, pass passwords={commit_id: password_bytes}.
A single password=b"..." is a fallback tried for every encrypted commit not
listed in passwords; a specific entry takes precedence. The algorithm is
read from each commit's descriptor.
from getpass import getpass
from pathlib import Path
import pyzarlib
password = getpass("Archive password: ").encode("utf-8")
inputs = [Path("secrets")]
for algorithm in ("aes-256-gcm", "chacha20-poly1305"):
archive = f"secrets-{algorithm}.zar"
pyzarlib.create_archive(
archive,
inputs,
password=password,
aead=algorithm,
)
check = pyzarlib.check_archive(archive, password=password)
entries = pyzarlib.list_archive(archive, password=password)
plan = pyzarlib.extract_archive(
archive,
f"restored-{algorithm}",
password=password,
dry_run=True,
)
print(algorithm, check["commits"], len(entries), len(plan["files"]))
In a real script, don't put a password in source code or command-line
arguments. The Python zarc-py CLI prompts without echo:
zarc-py create --password secrets-aes.zar secrets/
zarc-py create --password --aead chacha20-poly1305 secrets-chacha.zar secrets/
zarc-py check --password secrets-chacha.zar
zarc-py list --password secrets-chacha.zar
zarc-py extract --password --output restored/ secrets-chacha.zar
The archive stores the selected AEAD in its encryption descriptor. The
implementation creates fresh key/nonce material and uses Argon2id for
password-based key wrapping. Don't attempt to reuse nonces or store the
password in the archive. add_archive can append a new encrypted commit;
provide credentials for encrypted earlier commits when those commits need
validation. remove_archive and join_archive still reject encrypted archives
because encrypted stateful rewriting is not implemented.
Existing commits can be transformed over an inclusive commit-ID range. The
encryption function uses new_password for the resulting commits and accepts
password/passwords for the current passwords of any already-encrypted
commits. Decryption uses the current-password fields. Both support an optional
output path (otherwise the input is replaced atomically), AEAD/scope options
for encryption, and strict; when false, commits that lack a current password
are left unchanged.
pyzarlib.encrypt_archive_commits(
"backup.zar",
"00000002",
"00000003",
b"new-password",
output="encrypted-copy.zar",
aead="chacha20-poly1305",
passwords={"00000002": b"old-password"},
strict=True,
)
pyzarlib.decrypt_archive_commits(
"encrypted-copy.zar",
"00000002",
"00000003",
password=b"new-password",
strict=True,
)
Different passwords per commit
The global password is used as a fallback; explicit commit IDs override it.
Commit IDs are the eight-hex-digit values returned by info_archive.
commit_passwords = {
"00000001": b"older-commit-password",
"00000002": b"newer-commit-password",
}
entries = pyzarlib.list_archive("mixed.zar", passwords=commit_passwords)
contents = pyzarlib.extract_archive_to_memory(
"mixed.zar",
passwords=commit_passwords,
)
Data-only encryption
pyzarlib.create_archive(
"visible-header.zar",
["public-index.txt"],
password=b"data-password",
encryption_scope="data",
)
print(pyzarlib.info_archive("visible-header.zar")[0]["data_encrypted"])
Examples matching the zarc commands
These Python examples use the same operations as the zarc create, add,
remove, join, check, info, list, and extract commands. Run them from a working
directory containing src/, README.md, and any other referenced input
files. Inputs may be strings or pathlib.Path objects.
These examples use an unencrypted archive. Removing and joining encrypted
archives are not supported by the current high-level operations.
Create
Equivalent CLI: zarc create backup.zar src/ README.md
import pyzarlib
result = pyzarlib.create_archive("backup.zar", ["src", "README.md"])
print(f"Created using {result['block_size']} byte blocks")
Add or replace files
Equivalent CLI: zarc add backup.zar config.toml
import pyzarlib
pyzarlib.add_archive("backup.zar", ["config.toml"])
List and inspect commits
Equivalent CLI: zarc list backup.zar and zarc info backup.zar
import pyzarlib
for entry in pyzarlib.list_archive("backup.zar"):
print(entry["path"], entry["type"], entry.get("size", ""))
for commit in pyzarlib.info_archive("backup.zar"):
print(f"commit {commit['id']}: {commit['size']} bytes")
Check integrity
Equivalent CLI: zarc check backup.zar
import pyzarlib
report = pyzarlib.check_archive("backup.zar")
print(
f"{report['commits']} commits checked; "
f"{report['checked_blocks']} data blocks verified"
)
Extract files
Equivalent CLI: zarc extract backup.zar --output restored
import pyzarlib
plan = pyzarlib.extract_archive("backup.zar", "restored")
print(f"Extracted {len(plan['files'])} files")
Pass dry_run=True to preview the extraction without writing files.
Remove a path
Equivalent CLI: zarc remove backup.zar obsolete.txt
import pyzarlib
pyzarlib.remove_archive("backup.zar", ["obsolete.txt"])
Removal paths are archive-relative names, not filesystem paths to delete. Removing a directory also removes its descendants from the effective table of contents; earlier commits remain unchanged.
Join a commit range
Equivalent CLI: zarc join backup.zar --from <first-id> --to <last-id>
The IDs are the eight-hex-digit commit IDs returned by info_archive. This
example compacts the first two commits in physical order:
import pyzarlib
commits = pyzarlib.info_archive("backup.zar")
if len(commits) >= 2:
result = pyzarlib.join_archive(
"backup.zar",
commits[0]["id"],
commits[1]["id"],
)
print(f"Join completed with {len(result['warnings'])} warning(s)")
The range endpoints are inclusive and must identify a contiguous range in physical commit order.
API
Timestamp options are opt-in. Creation- or access-time recording fails if the filesystem does not provide it for a stored entry. Access times depend on filesystem policies and may change during reads. Imported archives use staging-time filesystem timestamps, and extraction does not restore them.
create_archive(archive, paths, *, strict=False, overwrite=False,save_metadata=False, save_modification_time=False, save_creation_time=False, save_access_time=False,include_special_files=False,verbose=False, block_size=8388608, compression_level=3, password=None,include_files=None, exclude_files=None, include_folders=None,exclude_folders=None)creates an archive and returns its resolved block size and warnings.add_archive(archive, paths, *, strict=False, save_metadata=False,save_modification_time=False, save_creation_time=False, save_access_time=False,include_special_files=False, verbose=False,block_size=8388608, compression_level=3, include_files=None,exclude_files=None, include_folders=None, exclude_folders=None)appends a commit and returns warnings.remove_archive(archive, paths)appends tombstones.join_archive(archive, from_id, to_id, *, block_size=8388608, compression_level=3)compacts a contiguous commit range and returns warnings.encrypt_archive_commits(archive, from_id, to_id, new_password, *, output=None, aead="aes-256-gcm", encryption_scope="header-and-data", password=None, passwords=None, strict=False)encrypts or re-encrypts an inclusive range.passwordandpasswordsunlock selected commits before re-encryption.decrypt_archive_commits(archive, from_id, to_id, *, output=None, password=None, passwords=None, strict=False)decrypts an inclusive range.check_archive(archive, *, recover=False, password=None)validates the archive and returns commit/block/recovery counts.info_archive(archive, *, verbose=False)returns commit size, compression, and optional detailed statistics.list_archive(archive, *, to=None, password=None)returns the effective TOC as dictionaries.extract_archive(archive, destination, *, dry_run=False, to=None, password=None, collision="rename", existing="error", restore_metadata=False, restore_symlinks=False, restore_devices=False, include_files=None, exclude_files=None, include_folders=None, exclude_folders=None)extracts selected entries and returns the resulting plan as dictionaries. Setdry_run=Trueto plan without writing files.read_custom_metadata(archive)returns the effective archive-level custom metadata as a dictionary.update_custom_metadata(archive, *, set=None, remove=None)sets and/or removes custom metadata keys and appends a metadata-only commit.extract_archive_to_memory(archive, *, to=None, password=None, size_limit=None, offset=0, include_files=None, exclude_files=None, include_folders=None, exclude_folders=None)returns a dictionary mapping archive-relative regular-file paths tobytes. The sameoffsetis applied to each file;size_limitcaps the number of bytes returned after that offset. Files are returned even when the offset is past end-of-file, in which case their value isb"". Directories, symlinks, pipes, and devices are omitted.
Password arguments accept bytes (or None). Input paths and destinations
accept strings and pathlib.Path values. Include/exclude arguments are
sequences of fnmatch patterns. Compression block size is 64 KiB through 32
MiB; block_size=0 requests automatic sizing. Zstandard compression levels
range from -7 through 22.
create_archive also accepts aead="aes-256-gcm" or
aead="chacha20-poly1305" when creating an encrypted archive; the default is
AES-256-GCM. This option selects the password wrapping and content AEAD
algorithm. Read operations use the algorithm recorded in the archive and need
only the matching password.
Long-running Rust operations release the Python GIL. The initial binding does not expose per-operation progress callbacks.
Metadata
Release files for pyzarlib 0.13.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 |
|---|---|---|---|---|
| pyzarlib-0.13.0.tar.gz | 201.4 kB | With provenance | Details for pyzarlib-0.13.0.tar.gz |
Built distributions (wheels)
Total release size: 65.3 MB
Release files / pyzarlib-0.13.0.tar.gz
| Download URL | pyzarlib-0.13.0.tar.gz |
|---|---|
| Size | 201.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
207d1802634a4429b07e947382ea5e2ff0d66c574bfe6689853bf76eec6bf1c6
|
|
BLAKE2b-256 checksum How to use checksums |
a99be295e355c293ad771426a30d79e0288befd1a8edaf35f611e0900432cc9e
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp315-cp315-win_arm64.whl
| Download URL | pyzarlib-0.13.0-cp315-cp315-win_arm64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.15 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
5d6a268bd4890b41633c8299e7ff32db6e1a766cc087847fbd212ce5cf4bd26a
|
|
BLAKE2b-256 checksum How to use checksums |
74d7c1995aaa31e56097982b8892b4219dd9fef3b4117630d6c9a0943ae3d91e
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp315-cp315-win_amd64.whl
| Download URL | pyzarlib-0.13.0-cp315-cp315-win_amd64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.15 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
da88acb007d8c933c832d46094d3611267e764580abc400e6c185484583d2b2e
|
|
BLAKE2b-256 checksum How to use checksums |
d2c9bd3d6bcc0171411219993c59f02ca19f2de44be41ff8fdfe7646123cfa56
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp315-cp315-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | pyzarlib-0.13.0-cp315-cp315-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.15 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
52b7445ceef63ce89c9bee498289fc3e5f11c1d211b11aba80b8d8e0b5a75d64
|
|
BLAKE2b-256 checksum How to use checksums |
7ef9bcd4df6c7ca597248e752abd2c10bed48bcb377449a813a5f37efd6429e9
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp315-cp315-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
| Download URL | pyzarlib-0.13.0-cp315-cp315-manylinux2014_aarch64.manylinux_2_17_aarch64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.15 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
e3fd4d4f678c9356ad80777ab6b26434dc7dc4c0a3c467d5d13979a219b52b17
|
|
BLAKE2b-256 checksum How to use checksums |
bd22413036017d444214ac0698dd9c26f711b15812981fb11484fb76fbbd769b
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp315-cp315-macosx_11_0_arm64.whl
| Download URL | pyzarlib-0.13.0-cp315-cp315-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.15 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
600060e5fc99ad36415f1cbdf021b6e762d77f7eb46302abc33561ff0a783d7f
|
|
BLAKE2b-256 checksum How to use checksums |
8e6298fae5ae31d869d01aa312da537ede9a3e2870929c0bbb3ec993f33c50a1
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp315-cp315-macosx_10_12_x86_64.whl
| Download URL | pyzarlib-0.13.0-cp315-cp315-macosx_10_12_x86_64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.15 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
3fe6d96d688adc5ce7e52d85e93350276a4530b4f095ac3545ab898f2fa708bc
|
|
BLAKE2b-256 checksum How to use checksums |
c77265086c61addedf557226f4931cbe77cb4736009a5f2a4abefa3e64210725
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp314-cp314-win_arm64.whl
| Download URL | pyzarlib-0.13.0-cp314-cp314-win_arm64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.14 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
0d50bb4335d1d22a8d39831fdde79a21d0cd9ecd45ccb32e2d822a7d740b58d4
|
|
BLAKE2b-256 checksum How to use checksums |
d4a955c3cf7e5da58008764bc5c29d03c6d2efcb0244a9fb42f3b79774e116d9
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp314-cp314-win_amd64.whl
| Download URL | pyzarlib-0.13.0-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
fee8e5b591ca153a81adc569b0438315d36bec2983599f7545761e084cd4dd3f
|
|
BLAKE2b-256 checksum How to use checksums |
a1e21d1a60a458057ce6c9e5e76f9e188cb35a4ca81130ca6f33f8f70dab312a
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | pyzarlib-0.13.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.14 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
9a3b83e6ced18abc7fdfbccf3e96388cfa094e76ce69e142114cb398451bc87c
|
|
BLAKE2b-256 checksum How to use checksums |
4edf0ad2743d028b8a6a2aee9a6d9f66c052b8dcb6cecfbe8de0d1aba47e3c55
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
| Download URL | pyzarlib-0.13.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.14 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
96f05c34317ddca5c2ff0a16f2973a0656f357fbeb3db505af7110e3b8557750
|
|
BLAKE2b-256 checksum How to use checksums |
ffae863830beef8f0e5e4893a1af48aeb999553bfd726eadb1b2188d20b92deb
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | pyzarlib-0.13.0-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
689e682137cf999c036d650957b8ae5b1323f3aa0e5ab2eb54334c0f0c7805fa
|
|
BLAKE2b-256 checksum How to use checksums |
c512f161a8627f4c6d770f8bbfc52a5e4537a5db9be70abde5144dd3acd0f1d0
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp314-cp314-macosx_10_12_x86_64.whl
| Download URL | pyzarlib-0.13.0-cp314-cp314-macosx_10_12_x86_64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.14 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
5aa0ead25f77528b48a27b1d8a1274d3ec5ffb43b68fe8dde81884477e01a613
|
|
BLAKE2b-256 checksum How to use checksums |
25ef29e054c9d42f65a35248a23739c3c1636bab8f2bb97a38c6bc3f7f75cff8
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp313-cp313-win_arm64.whl
| Download URL | pyzarlib-0.13.0-cp313-cp313-win_arm64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.13 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
c285e2f9d7c5bd113ae4e45766de3c16706d5267fb4eba0941d8f8f0a8f85412
|
|
BLAKE2b-256 checksum How to use checksums |
9c91cad7eab3e730eed28fba2bffc9096afbbd2f6034ff254ccd36f2bf365bca
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp313-cp313-win_amd64.whl
| Download URL | pyzarlib-0.13.0-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
09284fa67482d58cb870d37319cd2c8868f70e1c6d5a8bb8ae3b84cf76002f4e
|
|
BLAKE2b-256 checksum How to use checksums |
d1de912b5ea24d96fea7a0fd2caaea6b9493b93a8cd36d1f47a5400a7e21e836
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | pyzarlib-0.13.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
373d6aa01d2ac8532d5848c0dadef4f57f027a39e4667b09d2f8d78c1f46e461
|
|
BLAKE2b-256 checksum How to use checksums |
1705e7a1de3acb890665020ce106a52006141721bb1b149240ae276545cc3e5a
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
| Download URL | pyzarlib-0.13.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
34163d8fe848d9567eb8d4c729dccedfc120d0d10370e095983d42275ecb4a49
|
|
BLAKE2b-256 checksum How to use checksums |
455df9b564eceff8995da602e57b032c3e62a118cf8d2491ebc6e24f3b15b7cc
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | pyzarlib-0.13.0-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
d6772e4cce9be515149e4e4d327b374a12133bb784eb3c8223e1e115233fb1d5
|
|
BLAKE2b-256 checksum How to use checksums |
de873f556d84429caf40b1f4c2d70dee8fdf67c35b9712756b365993b1cdebff
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp313-cp313-macosx_10_12_x86_64.whl
| Download URL | pyzarlib-0.13.0-cp313-cp313-macosx_10_12_x86_64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.13 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
7eb8acc96c39087c818aca8722cee6b917fc9cc834792494974441b4f79194d8
|
|
BLAKE2b-256 checksum How to use checksums |
46acb3c156fa59a491bbbf5fe559a6e057438cd48a8dfe1db0993e700608fefe
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp312-cp312-win_arm64.whl
| Download URL | pyzarlib-0.13.0-cp312-cp312-win_arm64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.12 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
2f1de5f1a6968fc580c5f2d892651905028733a4a1e6f8fd6e0084260dbfa78e
|
|
BLAKE2b-256 checksum How to use checksums |
640f19a359425b6aa0b16e32be186cfa9b2e5c7f467bb36805b27143e78bc75c
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp312-cp312-win_amd64.whl
| Download URL | pyzarlib-0.13.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
f05569b91bd1368242266e84b672b438d2153e3c1caa0aabc8b8e6345fc0d92c
|
|
BLAKE2b-256 checksum How to use checksums |
000e15eea945f9febd2d889709e865610b57c1f934e4de39822d22f6ff21db70
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | pyzarlib-0.13.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
b253f6bebabdea509820638d77f0adbe345fc4c5c3dd04c459cd292a7f4ba30c
|
|
BLAKE2b-256 checksum How to use checksums |
b65d44fb4e633c98836a1f73e6c10510073842687f9f8a7c6140d84de19371ca
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
| Download URL | pyzarlib-0.13.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
5a875c4411f5ecb51803841ebd1b5add0151860b387c8d597c492a150bf5dd2d
|
|
BLAKE2b-256 checksum How to use checksums |
a0f8c515b7b4cc6e50447aa2c912007bb93615e6ca4d42cbd2c02a43182657a1
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | pyzarlib-0.13.0-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
a186f8f8cbf2fd57fcd934608c2c776b170e531537d0f31391b9464ff09c1fd2
|
|
BLAKE2b-256 checksum How to use checksums |
64069f62129b0fe0ad96ca755f141f23cb1790d6392bd3feb98a2b4ea2f353f4
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp312-cp312-macosx_10_12_x86_64.whl
| Download URL | pyzarlib-0.13.0-cp312-cp312-macosx_10_12_x86_64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.12 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
feb7d2b4a17e9620efd2b5b494aaca9a012155f6a756db222afccda94dff1ade
|
|
BLAKE2b-256 checksum How to use checksums |
86a4c2e3fce8c356105dc2ce449f1b1c591fd4c7da6fdc96136cb45381f62893
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp311-cp311-win_arm64.whl
| Download URL | pyzarlib-0.13.0-cp311-cp311-win_arm64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.11 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
40aac7462b3f5c98a545c60c7513ec2f9ef0ad1fd1ee7d6103f8af645454309c
|
|
BLAKE2b-256 checksum How to use checksums |
f63f42eb81ea416b768a5517a7d0fa360dd134354616c548d7a9e92b0b185e3b
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp311-cp311-win_amd64.whl
| Download URL | pyzarlib-0.13.0-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
fa4835c9bf333f32ff5542f485f531afbef8ff3b67237e472ffc257a72ec614c
|
|
BLAKE2b-256 checksum How to use checksums |
07c0341a839b1378caed35e2e9bf2d5690a10645f61b01cd3fba9ad0e9d53358
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | pyzarlib-0.13.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
a473f643d65ea9de66f7fd3d2156a866caa7f75cbf50afe265e00169f58d62cc
|
|
BLAKE2b-256 checksum How to use checksums |
cb6e9f2e5cc0a45b6656967d28513c2d4b208649ebd418df2ece6c56afb88604
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
| Download URL | pyzarlib-0.13.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
1523d9561ddb9bc7ee44f6119ce574f451b787d85c94585aac26d1928efa7685
|
|
BLAKE2b-256 checksum How to use checksums |
2dade60f2642339ab9b96eef9012227b31a9327d18edce9a6e992970609df6d6
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | pyzarlib-0.13.0-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
75adf06c06dc1fa0ede03b29d970e68b7033acaa0290576053154ea3989f39b4
|
|
BLAKE2b-256 checksum How to use checksums |
80004ae4dca44f5e15d789fb22abfb18b87192afd5aa5fd71b0ed1ff9caba134
|
| 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 15, 2026.
Transparency logRelease files / pyzarlib-0.13.0-cp311-cp311-macosx_10_12_x86_64.whl
| Download URL | pyzarlib-0.13.0-cp311-cp311-macosx_10_12_x86_64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.11 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
1d1d991633781932a6f0eb50136962e10c63f43250787dcb79048a23e8a22851
|
|
BLAKE2b-256 checksum How to use checksums |
f146f484f934d65676c3039c3b3b75ba90176c142558a401fcd3448aebc34fa4
|
| 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 15, 2026.
Transparency logSecurity for pyzarlib 0.13.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
All 31 files in this release have been uploaded with provenance metadata.
Attestation for pyzarlib-0.13.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 15, 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.