docker-pkg-images builds docker images from templates.
1 maintainer
Metadata
1 maintainer
Release files for docker-pkg 4.0.4
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 | |
|---|---|---|---|---|
| docker_pkg-4.0.4.tar.gz | 41.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| docker_pkg-4.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 83.9 kB
Release files / docker_pkg-4.0.4.tar.gz
| Download URL | docker_pkg-4.0.4.tar.gz |
|---|---|
| Size | 41.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
87f88c1f9a4db7722fd4692ebd6041423ac76513250f1a09924744cb205f9378
|
|
BLAKE2b-256 checksum How to use checksums |
781af545fb8355766c677a7a61779ac809493ff827da12f9980374a36aac6095
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Release files / docker_pkg-4.0.4-py3-none-any.whl
| Download URL | docker_pkg-4.0.4-py3-none-any.whl |
|---|---|
| Size | 42.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f7ead1cd6c0357c0fcfb8fab0b93f02bf1f1fcb2905e3696a7c1106652caf9ba
|
|
BLAKE2b-256 checksum How to use checksums |
2d576663c1bf813e51585eb223b046f391e1a11f68f24ee564a1d490ba38c91e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Security for docker-pkg 4.0.4
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.
