Metadata
Release files for rapydo-http 3.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 | |
|---|---|---|---|---|
| rapydo_http-3.0.tar.gz | 176.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rapydo_http-3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 415.5 kB
Release files / rapydo_http-3.0.tar.gz
| Download URL | rapydo_http-3.0.tar.gz |
|---|---|
| Size | 176.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f65fc3483f0cc942d10d3216c2901efaea318a2acd072eff97190ffc3a9dad6f
|
|
BLAKE2b-256 checksum How to use checksums |
b0cf5ef1617098d4e71d3a0f457c6da468a08bf98018c012a75fcfe84da0178f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.9.19
|
Release files / rapydo_http-3.0-py3-none-any.whl
| Download URL | rapydo_http-3.0-py3-none-any.whl |
|---|---|
| Size | 239.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
702ba6791bbb6ca0b79bf3216d9e88ef53ac37c58cdcfc2d5ecc6de3f829f209
|
|
BLAKE2b-256 checksum How to use checksums |
6a8843f5aebba9cef6ac81104644910a962348c2d55331cd6b8b77f79adc9a7a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.9.19
|
Security for rapydo-http 3.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.