Metadata
Release files for amsphyslab-tools 0.3.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 | |
|---|---|---|---|---|
| amsphyslab-tools-0.3.0.tar.gz | 14.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| amsphyslab_tools-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.3 kB
Release files / amsphyslab-tools-0.3.0.tar.gz
| Download URL | amsphyslab-tools-0.3.0.tar.gz |
|---|---|
| Size | 14.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c7aa3dfa628fc77ea279f43a065d5fb58ca2df82563d6aa14718107aef677f9d
|
|
BLAKE2b-256 checksum How to use checksums |
e4969b4c48c32c2a51a7e442a0948d8780382f0e3264d12ab839596cc278a560
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.4 CPython/3.7.9 Darwin/20.2.0
|
Release files / amsphyslab_tools-0.3.0-py3-none-any.whl
| Download URL | amsphyslab_tools-0.3.0-py3-none-any.whl |
|---|---|
| Size | 14.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
74c622704317ba18244104c7ec889c9dbd04991075123c0a439c14a9920b08d2
|
|
BLAKE2b-256 checksum How to use checksums |
824f3eb8cf4538a5f7c27eea43d61a5524473bee40e420f5dc437d95afe44178
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.4 CPython/3.7.9 Darwin/20.2.0
|
Security for amsphyslab-tools 0.3.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.