The author of this package has not provided a project description
Metadata
Release files for dbs3-pycurl 3.18.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 | |
|---|---|---|---|---|
| dbs3_pycurl-3.18.3.tar.gz | 13.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dbs3_pycurl-3.18.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.1 kB
Release files / dbs3_pycurl-3.18.3.tar.gz
| Download URL | dbs3_pycurl-3.18.3.tar.gz |
|---|---|
| Size | 13.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d2e53c942d19c40ef0845c904729d181f8b5cc32fae1adaf520aafd2bbb3b299
|
|
BLAKE2b-256 checksum How to use checksums |
9e65a20d4a7d0f492775fb2837228c7990bf3f8bc5df46e44acaf9e30bbe4319
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
Release files / dbs3_pycurl-3.18.3-py3-none-any.whl
| Download URL | dbs3_pycurl-3.18.3-py3-none-any.whl |
|---|---|
| Size | 12.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a7ce693338365245d5687e4c720652cb326e9d5de2b257d55fdddd7cbb5be2a1
|
|
BLAKE2b-256 checksum How to use checksums |
ca43da95de8d1d1c510c3c40b32fc54f2575ae5b9d36a726a36e31bb59172518
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
Security for dbs3-pycurl 3.18.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.