The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for docker-automator 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 | |
|---|---|---|---|---|
| docker_automator-0.1.tar.gz | 1.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| docker_automator-0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.8 kB
Release files / docker_automator-0.1.tar.gz
| Download URL | docker_automator-0.1.tar.gz |
|---|---|
| Size | 1.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9129f4c9b95f5c5ff8028d5e8abb235f2bbc8f441f38e8e8520a05b569bee761
|
|
BLAKE2b-256 checksum How to use checksums |
d7f3ac7e31b154f3aca61658860fb2d7b0778162a69d6aa105c048d7c4ba196e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Release files / docker_automator-0.1-py3-none-any.whl
| Download URL | docker_automator-0.1-py3-none-any.whl |
|---|---|
| Size | 1.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
27bd870aa9034385161ef3059110e8f8e1d9edd50b913e35eb518b436ac0bba5
|
|
BLAKE2b-256 checksum How to use checksums |
49a24b15c7219b7a7de9c4245fd13ca29374868f9c7da7fd70ef02443958ee1a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Security for docker-automator 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.
