The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for tote 0.1.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 | |
|---|---|---|---|---|
| tote-0.1.0.tar.gz | 777 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tote-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.8 kB
Release files / tote-0.1.0.tar.gz
| Download URL | tote-0.1.0.tar.gz |
|---|---|
| Size | 777 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5da0c6baf14954f7391e499b49b8a66248597360958b5bb48c841adb835ec1a4
|
|
BLAKE2b-256 checksum How to use checksums |
361eac28c464b5ebdae16f12d76e37842c88f72b793658b60569d3999cef8cf4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.0a2 CPython/3.7.2 Darwin/18.2.0
|
Release files / tote-0.1.0-py3-none-any.whl
| Download URL | tote-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
75cd354809a3c0374d09f4d9a96c4c2d2b1fd8c9423c108d2166e7aaafdef19a
|
|
BLAKE2b-256 checksum How to use checksums |
8b4d6fd6ac4be355f2c74ffd7a1faccd4b7aa04bd5215204511f5748a02eca7c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.0a2 CPython/3.7.2 Darwin/18.2.0
|
Security for tote 0.1.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.
