Metadata
Release files for pkgexampledatafiles 0.0.3
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 | |
|---|---|---|---|---|
| pkgexampledatafiles-0.0.3.tar.gz | 3.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pkgexampledatafiles-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.1 kB
Release files / pkgexampledatafiles-0.0.3.tar.gz
| Download URL | pkgexampledatafiles-0.0.3.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1a3d3957105a2182dd012b0d12153a91c0e1f03290075ac9408910f629ea19be
|
|
BLAKE2b-256 checksum How to use checksums |
64bbcdca090940c24fd814c3f7eb3e3ee7104ee787a9c9d2ea59785ed5c4ac0f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.6
|
Release files / pkgexampledatafiles-0.0.3-py3-none-any.whl
| Download URL | pkgexampledatafiles-0.0.3-py3-none-any.whl |
|---|---|
| Size | 4.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
10a556a6543f8d99181700042faf87f79531aff254de9f05bab98b26d4c37b50
|
|
BLAKE2b-256 checksum How to use checksums |
fae7cf99871c1fc77e52f61ffcbdf2f60853834acc4234012cec0dae2fd006be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.6
|
Security for pkgexampledatafiles 0.0.3
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.