The author of this package has not provided a project description
Metadata
Release files for caddy-python 0.0.54
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 | |
|---|---|---|---|---|
| caddy-python-0.0.54.tar.gz | 4.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| caddy_python-0.0.54-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.5 kB
Release files / caddy-python-0.0.54.tar.gz
| Download URL | caddy-python-0.0.54.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a451043b799c71043e0c0b6399b6a6017081e0e67e728e88e221a983cdf958d0
|
|
BLAKE2b-256 checksum How to use checksums |
776740124e5c5da4c5293f6f955badeab107faf07e01bda24201a0dc2331015b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.6
|
Release files / caddy_python-0.0.54-py3-none-any.whl
| Download URL | caddy_python-0.0.54-py3-none-any.whl |
|---|---|
| Size | 4.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
891a44d4fc69a1b9945f607f8cc95ee022e55ae57902fd1b1cc61d0c0b39cc75
|
|
BLAKE2b-256 checksum How to use checksums |
da70c75ef475a9cc5bd97ccc37ff08d92cb0e7ca746e8a6308f1257bce9a983f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.6
|
Security for caddy-python 0.0.54
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.