My first Python package
Metadata
Release files for armanfirstpackage 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 | |
|---|---|---|---|---|
| armanfirstpackage-0.0.3.tar.gz | 1.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| armanfirstpackage-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.3 kB
Release files / armanfirstpackage-0.0.3.tar.gz
| Download URL | armanfirstpackage-0.0.3.tar.gz |
|---|---|
| Size | 1.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
be63216d7415d4f2ccc05e7f865d60a87805080a10171ac3c47cc56f4972790a
|
|
BLAKE2b-256 checksum How to use checksums |
7dec7885949bd73d5ee2a0bd1ff5a907c1156badf48e0bde9f3ef4c5a94e81ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Release files / armanfirstpackage-0.0.3-py3-none-any.whl
| Download URL | armanfirstpackage-0.0.3-py3-none-any.whl |
|---|---|
| Size | 2.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ce163efab565115cf464714cb5218973db23c9eb3fea01e8d3771c26e03ca5a7
|
|
BLAKE2b-256 checksum How to use checksums |
9e9bdb416e4ff9f98abf1822142fcd3f4a76836113fd396cb6483878e3a8d635
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Security for armanfirstpackage 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.