The author of this package has not provided a project description
Metadata
Release files for Adding-Test 0.1.1
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 | |
|---|---|---|---|---|
| Adding_Test-0.1.1.tar.gz | 911 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| Adding_Test-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.3 kB
Release files / Adding_Test-0.1.1.tar.gz
| Download URL | Adding_Test-0.1.1.tar.gz |
|---|---|
| Size | 911 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd81e6d8ea917703ec1444c00b242017f87f3b26b940df5cc18ee3c49d98aaa6
|
|
BLAKE2b-256 checksum How to use checksums |
1eb3b0938f9c4b2a577de7f9b676d8003900b503fad54c60040a6e6a93e5d84c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.10
|
Release files / Adding_Test-0.1.1-py3-none-any.whl
| Download URL | Adding_Test-0.1.1-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f67feed47fc9c9df9665ba4f1b8db365beba057b8e8d3f535d3f43690cbf8f13
|
|
BLAKE2b-256 checksum How to use checksums |
d4a81d5855ee616a674040c463897dac54d07be7cbeaad419e7972f8b6aa488b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.10
|
Security for Adding-Test 0.1.1
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.