The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for quadkit-http 0.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 | |
|---|---|---|---|---|
| quadkit_http-0.0.1.tar.gz | 382 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| quadkit_http-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 kB
Release files / quadkit_http-0.0.1.tar.gz
| Download URL | quadkit_http-0.0.1.tar.gz |
|---|---|
| Size | 382 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7b0a7f7ad627a444c8e00ba86f4a6f09e6dc607e31b355dcc4312b7d8663f170
|
|
BLAKE2b-256 checksum How to use checksums |
e604547a561665a579af44f70d9da6164ab2a40d4672fcf64404c486728397b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Release files / quadkit_http-0.0.1-py3-none-any.whl
| Download URL | quadkit_http-0.0.1-py3-none-any.whl |
|---|---|
| Size | 993 Bytes |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
910d7966b32d6956fbe4e528bb8a6d449d0b0d11dbd78ccd729f296dfc51e890
|
|
BLAKE2b-256 checksum How to use checksums |
3564d1f17a29c74bde02e464a5a3027ceecb843a8e5392c55fe3519ea5bf6e13
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Security for quadkit-http 0.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.
