# This is the homepage of the ‘bakerpdf’ project
We will put more codes here.
1 maintainer
Metadata
1 maintainer
Release files for bakerpdf 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 | |
|---|---|---|---|---|
| bakerpdf-0.1.0.tar.gz | 14.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bakerpdf-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.4 kB
Release files / bakerpdf-0.1.0.tar.gz
| Download URL | bakerpdf-0.1.0.tar.gz |
|---|---|
| Size | 14.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e0f8c8d8ef07da4ebdc00f4646291981142f7f704bd6d732a5297975b15a055a
|
|
BLAKE2b-256 checksum How to use checksums |
3ce508b74b42d843002fcc12d53d7133c57c0bc3feb1934c84d14ba7dcd72880
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.12.2
|
Release files / bakerpdf-0.1.0-py3-none-any.whl
| Download URL | bakerpdf-0.1.0-py3-none-any.whl |
|---|---|
| Size | 14.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f2187a99f38bd402ecafaf6b1e0190af2385409f69935fc715ff9c3492da169e
|
|
BLAKE2b-256 checksum How to use checksums |
44d10ee9d3aec74f5a51603645af4ccb01849facfb83fac80fec4e921d5a488c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.12.2
|
Security for bakerpdf 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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.
