The author of this package has not provided a project description
Metadata
Release files for bloodymary 0.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 | |
|---|---|---|---|---|
| bloodymary-0.2.tar.gz | 4.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bloodymary-0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.9 kB
Release files / bloodymary-0.2.tar.gz
| Download URL | bloodymary-0.2.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c610e77320595ac7e87760e083e8128dd1dac09d32529a42873acd7369852976
|
|
BLAKE2b-256 checksum How to use checksums |
899263ee3510ec1aacf462a44d6d33907f9e6a738d61676e5d649950a8efe78d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.14 CPython/3.10.5 Darwin/21.6.0
|
Release files / bloodymary-0.2-py3-none-any.whl
| Download URL | bloodymary-0.2-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
be3edeb05a678375e0627bb3e59bb5a3b12ba05f210d7cf318d099b31b48f6a8
|
|
BLAKE2b-256 checksum How to use checksums |
b229bf72360028804fe7f424989bba7093f3867ce563bb2df5c2499219431b82
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.14 CPython/3.10.5 Darwin/21.6.0
|
Security for bloodymary 0.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.