Metadata
Release files for basic-calculator-pkg 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 | |
|---|---|---|---|---|
| basic_calculator_pkg-0.1.0.tar.gz | 1.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| basic_calculator_pkg-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.1 kB
Release files / basic_calculator_pkg-0.1.0.tar.gz
| Download URL | basic_calculator_pkg-0.1.0.tar.gz |
|---|---|
| Size | 1.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
faedf8fc9bc8440abe31883284cc72e7ee5b7ae5dbedc9b0dd668f5bab328c24
|
|
BLAKE2b-256 checksum How to use checksums |
d4018015a8bd72abeb20e6b3e1a36cbf4f1389d8ce6a208b66030789790d1240
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.16
|
Release files / basic_calculator_pkg-0.1.0-py3-none-any.whl
| Download URL | basic_calculator_pkg-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
735b787b85c365d7727b201fe083b029ffc195280cb90a969fb36d7e4b5fbd3a
|
|
BLAKE2b-256 checksum How to use checksums |
a232814682a22df098cb4155537385dee42c34d9b888c9cc050bd34c5feffda1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.16
|
Security for basic-calculator-pkg 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.