The author of this package has not provided a project description
2 maintainers
Metadata
2 maintainers
Release files for up-tamer 1.1.6
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 | |
|---|---|---|---|---|
| up_tamer-1.1.6.tar.gz | 13.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| up_tamer-1.1.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.8 kB
Release files / up_tamer-1.1.6.tar.gz
| Download URL | up_tamer-1.1.6.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
25090b15d2008ce07ac73b2a2b9eb934ae50616104fa1580d872687e912e4bb6
|
|
BLAKE2b-256 checksum How to use checksums |
f17ac9bc61e54bef5fc3915f6bba9d43b59cc3bec2dde226fadb77b9b6c2d820
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / up_tamer-1.1.6-py3-none-any.whl
| Download URL | up_tamer-1.1.6-py3-none-any.whl |
|---|---|
| Size | 14.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c36a4ba896c33ab64852a0f98d0aef835648eb1f55d450030dd506bd36ed5ea6
|
|
BLAKE2b-256 checksum How to use checksums |
e63bce1efba1196ec879017a8ae04e96d38557570a06f75ed02138343e5239f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for up-tamer 1.1.6
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.
