The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for paratools 0.0.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 | |
|---|---|---|---|---|
| paratools-0.0.1.tar.gz | 2.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| paratools-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.1 kB
Release files / paratools-0.0.1.tar.gz
| Download URL | paratools-0.0.1.tar.gz |
|---|---|
| Size | 2.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
44e80f4464dc6a761f69a0cd8b99ea29981b6ce870454756c5511c7059c7215a
|
|
BLAKE2b-256 checksum How to use checksums |
c096c7965def28ff5d20762e4122759bc696f989058539a84064ad15787f3ad1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Release files / paratools-0.0.1-py3-none-any.whl
| Download URL | paratools-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e6901ec4530ea43922a337927418229cdf47e28b1985cbcdac95497b91bddec1
|
|
BLAKE2b-256 checksum How to use checksums |
9e67393030a9840aa20453e2a1812bc6571c3728e0b988e2a92bf3dc63974401
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Security for paratools 0.0.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.
