Skip to main content

The author of this package has not provided a project description

Metadata

Release files for pith-pdf 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distributions (wheels)

Table of built distributions (wheels) for pith-pdf 0.1.0
File Actions
pith_pdf-0.1.0-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for pith_pdf-0.1.0-cp313-cp313-win_amd64.whl
pith_pdf-0.1.0-cp313-cp313-manylinux_2_34_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.34+ x86-64 Details for pith_pdf-0.1.0-cp313-cp313-manylinux_2_34_x86_64.whl
pith_pdf-0.1.0-cp313-cp313-macosx_11_0_universal2.whl CPython 3.13 CPython 3.13 macOS 11.0+ universal2 (ARM64, x86-64) Details for pith_pdf-0.1.0-cp313-cp313-macosx_11_0_universal2.whl
pith_pdf-0.1.0-cp312-cp312-manylinux_2_34_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.34+ x86-64 Details for pith_pdf-0.1.0-cp312-cp312-manylinux_2_34_x86_64.whl

Total release size: 1.0 MB

Release files / pith_pdf-0.1.0-cp313-cp313-win_amd64.whl

Download URL pith_pdf-0.1.0-cp313-cp313-win_amd64.whl
Size 174.7 kB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
bbd7528e34baf2ad3b3eaa27b4e5ad34bd96a35ec0e9dddb57cdc0d21b04c311
BLAKE2b-256 checksum
How to use checksums
a95477eb9c308e580a0a04f706452cbfffa3071c6cf038c669a15f181aeb2440
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 14, 2026.

Transparency log

Release files / pith_pdf-0.1.0-cp313-cp313-manylinux_2_34_x86_64.whl

Download URL pith_pdf-0.1.0-cp313-cp313-manylinux_2_34_x86_64.whl
Size 303.5 kB
Tags CPython 3.13 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
b64294e4b42109dfc97bc2dba61da8572fcde27f449bcd1dbe51352747f3852a
BLAKE2b-256 checksum
How to use checksums
3be5b06a2bec9c145f06df5eed76e397b6c5d462a00a08d12b954a3e0438a016
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 14, 2026.

Transparency log

Release files / pith_pdf-0.1.0-cp313-cp313-macosx_11_0_universal2.whl

Download URL pith_pdf-0.1.0-cp313-cp313-macosx_11_0_universal2.whl
Size 260.7 kB
Tags CPython 3.13 macOS 11.0+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
96b74060345563329b88acb08a9b2e01a84ec20e5160db4997c487b4df17dd56
BLAKE2b-256 checksum
How to use checksums
30f33315ec7241930bbc0de782c3e723affb59195cd23734ba3f4129a51a6b48
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 14, 2026.

Transparency log

Release files / pith_pdf-0.1.0-cp312-cp312-manylinux_2_34_x86_64.whl

Download URL pith_pdf-0.1.0-cp312-cp312-manylinux_2_34_x86_64.whl
Size 303.5 kB
Tags CPython 3.12 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
d51dbdbf18c951ac21f22a18179bfe55fc4c6618e14bcf91487969f6a692de6c
BLAKE2b-256 checksum
How to use checksums
11bcb55ee9c6e483eb89d6b43c3bbe8cff5c2fbc3a81ee3f547b51ea37d93ac0
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 9, 2026.

Transparency log

Security for pith-pdf 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

All 4 files in this release have been uploaded with provenance metadata.

Select from 4 files

Attestation for pith_pdf-0.1.0-cp313-cp313-win_amd64.whl

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 14, 2026.

Transparency log

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page