Packeage teste
1 maintainer
Metadata
1 maintainer
Release files for attemptrequestslib 0.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 | |
|---|---|---|---|---|
| attemptrequestslib-0.1.tar.gz | 3.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| attemptrequestslib-0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.2 kB
Release files / attemptrequestslib-0.1.tar.gz
| Download URL | attemptrequestslib-0.1.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
665286188b9dce37ffed0c1d87cca8ae7ed7f374bc601399b835717d93677209
|
|
BLAKE2b-256 checksum How to use checksums |
a58322f68c3e6d6f2307adf80836911339f110c7226437688c70643d3f856ec2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.7
|
Release files / attemptrequestslib-0.1-py3-none-any.whl
| Download URL | attemptrequestslib-0.1-py3-none-any.whl |
|---|---|
| Size | 4.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
20059a1f85ab4ae601f5e49cb41e0ee50a8b9dad0e4cd163040850464d14aa32
|
|
BLAKE2b-256 checksum How to use checksums |
f69321f0110b29d36cfedb6145af8a17ca4fb64ef6796a690acce0eb72ebc404
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.7
|
Security for attemptrequestslib 0.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.
