Example Package
This is a simple example package. You can use Github-flavored Markdown to write your content.
1 maintainer
Metadata
1 maintainer
Release files for at-8257 0.0.2
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 | |
|---|---|---|---|---|
| at_8257-0.0.2.tar.gz | 2.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| at_8257-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.2 kB
Release files / at_8257-0.0.2.tar.gz
| Download URL | at_8257-0.0.2.tar.gz |
|---|---|
| Size | 2.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5fb71b30225e70742228b188e96f924c644a09398ea866f218bbd2b181702a2d
|
|
BLAKE2b-256 checksum How to use checksums |
bb0875d464f7c5531d72d2324fa642db1452c4cbac274320412884cd8d9d314e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.10
|
Release files / at_8257-0.0.2-py3-none-any.whl
| Download URL | at_8257-0.0.2-py3-none-any.whl |
|---|---|
| Size | 2.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c687394c5ffb1dae5954ab2dead444d6758efd557c260d5382d39af5bef9193c
|
|
BLAKE2b-256 checksum How to use checksums |
ca5d12e5976e6a86d20b6194eec71f04ba9683d67a93f827aa1507f6132e100d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.10
|
Security for at-8257 0.0.2
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.
