The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for runbook-emad-te 0.1.2
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 | |
|---|---|---|---|---|
| runbook_emad_te-0.1.2.tar.gz | 4.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| runbook_emad_te-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.7 kB
Release files / runbook_emad_te-0.1.2.tar.gz
| Download URL | runbook_emad_te-0.1.2.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3aa5875a6bf5f948de0352897dcb20adc24e5dfc6c1cac6eca5ff6d48123f717
|
|
BLAKE2b-256 checksum How to use checksums |
40eb8b9a0b817cb4182207b15cae14369ca81a38e0ee9b2186a958ee0582e923
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Release files / runbook_emad_te-0.1.2-py3-none-any.whl
| Download URL | runbook_emad_te-0.1.2-py3-none-any.whl |
|---|---|
| Size | 5.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f3efeed550878bf4c93ca2bd973abff6b8fc4615b89051de547f72f5ae5ba04d
|
|
BLAKE2b-256 checksum How to use checksums |
cc1191f75a1b1750983d5424981dc183e322b021f5e70820ac0c2493005a6f42
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for runbook-emad-te 0.1.2
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.
