content file here
1 maintainer
Metadata
1 maintainer
Release files for baptiste 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 | |
|---|---|---|---|---|
| baptiste-0.1.0.tar.gz | 772 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| baptiste-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.1 kB
Release files / baptiste-0.1.0.tar.gz
| Download URL | baptiste-0.1.0.tar.gz |
|---|---|
| Size | 772 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
43aab1c400722322840f1440ba09785821e4685c12f115bdb1c0ad25f1b9e5d4
|
|
BLAKE2b-256 checksum How to use checksums |
ddf03c4d342ad85098028f0e6708aaa1f6ab64e18399b8995f10ec97bb98c829
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.10.15 Linux/6.8.0-1014-azure
|
Release files / baptiste-0.1.0-py3-none-any.whl
| Download URL | baptiste-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6a54fdaff8e50f8a77420e28360c293ee7eaea30c5c70a15a697c1ce6ffca68b
|
|
BLAKE2b-256 checksum How to use checksums |
3c923aa90a8a2271ecbd299bc096a7b3b67c175925fd19ee73e03221bc1a8e6f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.10.15 Linux/6.8.0-1014-azure
|
Security for baptiste 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.
