Metadata
Release files for aerosense-tools 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 | |
|---|---|---|---|---|
| aerosense-tools-0.1.0.tar.gz | 2.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aerosense_tools-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.7 kB
Release files / aerosense-tools-0.1.0.tar.gz
| Download URL | aerosense-tools-0.1.0.tar.gz |
|---|---|
| Size | 2.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e0b9ea791c3bb3dd657dd755a9de7415e52949563da8ff716ee81667c5355872
|
|
BLAKE2b-256 checksum How to use checksums |
0f13ff179cba33c4cbf1b540594c7300552c82c306a50f9947bbccf849356653
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.6 CPython/3.9.1 Darwin/21.2.0
|
Release files / aerosense_tools-0.1.0-py3-none-any.whl
| Download URL | aerosense_tools-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
09ce7f9f8467c8a7db378124b28c66296aa25a2e4e6083fd74163a323fa2e404
|
|
BLAKE2b-256 checksum How to use checksums |
a60b9112bbfa61c224399c32afe8efaa288db14a5de4d8fe244614cd8f9ace40
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.6 CPython/3.9.1 Darwin/21.2.0
|
Security for aerosense-tools 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.