The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for utaseyu 0.0.0
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 | |
|---|---|---|---|---|
| utaseyu-0.0.0.tar.gz | 721 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| utaseyu-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.7 kB
Release files / utaseyu-0.0.0.tar.gz
| Download URL | utaseyu-0.0.0.tar.gz |
|---|---|
| Size | 721 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a115ec8d24a7f4016d2308251bc6d8a68d237a50c4b8f148c62afcf2604ec397
|
|
BLAKE2b-256 checksum How to use checksums |
246e77b017e24b0db0f42e06bf66414d36f36ce9e23dba952a1336a3ef5c5620
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / utaseyu-0.0.0-py3-none-any.whl
| Download URL | utaseyu-0.0.0-py3-none-any.whl |
|---|---|
| Size | 949 Bytes |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1758442bce04d2716902a2db1f46f09a8b205f117ac85a757b999039d267c838
|
|
BLAKE2b-256 checksum How to use checksums |
8174645bbbe12d1c5ed84e7fb6cacb7d110bec10651c4abb0dbef2c411276148
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for utaseyu 0.0.0
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.
