The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for beautifish 2.2.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 | |
|---|---|---|---|---|
| beautifish-2.2.1.tar.gz | 5.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| beautifish-2.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.8 kB
Release files / beautifish-2.2.1.tar.gz
| Download URL | beautifish-2.2.1.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
724d4a112f228a21760818ab7b5b465b8d03826f6e2bdf1163e498a92a67292d
|
|
BLAKE2b-256 checksum How to use checksums |
9e1b5b224ae6e97ced8093ea3c7d0063c1472daed6bd49a50121eedec5c35d14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.0
|
Release files / beautifish-2.2.1-py3-none-any.whl
| Download URL | beautifish-2.2.1-py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3b1536c943523b384ec0533648cab729ad83729a23bc7dd01b7d483b973a467c
|
|
BLAKE2b-256 checksum How to use checksums |
6c7c555e6871f7720b497b8330944433583123f497d094ab24313e4c3e4daa3f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.0
|
Security for beautifish 2.2.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.
