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