Apache plugin for Certbot
4 maintainers
Metadata
4 maintainers
Release files for certbot-apache 5.8.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 | |
|---|---|---|---|---|
| certbot_apache-5.8.0.tar.gz | 6.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| certbot_apache-5.8.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.4 kB
Release files / certbot_apache-5.8.0.tar.gz
| Download URL | certbot_apache-5.8.0.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c09403208a749b2bf1bb03051886d6e926572f113a93326ae39895a443d43a46
|
|
BLAKE2b-256 checksum How to use checksums |
30d02b3179b009bfd0f79d0b853be71a4e36ff5fde9c28d4752f3a5eaa513b81
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.3
|
Release files / certbot_apache-5.8.0-py3-none-any.whl
| Download URL | certbot_apache-5.8.0-py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
da9a24d94b7c34777a74a40e2a8d23f03ee086eed2f3f14632b2fc2fd1f9f66d
|
|
BLAKE2b-256 checksum How to use checksums |
25079f16ba06b456300fa4ee8c85ef36a456cfc11486ee9cb67bc8544a0f67c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.3
|
Security for certbot-apache 5.8.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.
