The author of this package has not provided a project description
Metadata
Release files for ica-aroma-py 0.1.3
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 | |
|---|---|---|---|---|
| ica_aroma_py-0.1.3.tar.gz | 73.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ica_aroma_py-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 146.4 kB
Release files / ica_aroma_py-0.1.3.tar.gz
| Download URL | ica_aroma_py-0.1.3.tar.gz |
|---|---|
| Size | 73.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ef051fc7cf7493c63c68738525b9038ca8c3932d4179b7e1b371f74512ba31b8
|
|
BLAKE2b-256 checksum How to use checksums |
ebfcc5240bf95f633ee1d78947704939758abfab2cf64c89792e54d1c5128c6c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.9
|
Release files / ica_aroma_py-0.1.3-py3-none-any.whl
| Download URL | ica_aroma_py-0.1.3-py3-none-any.whl |
|---|---|
| Size | 73.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9a8666eff11751623bc196fdb04c3745a0390369d06558b4b95f9b62ec2c18ff
|
|
BLAKE2b-256 checksum How to use checksums |
f13ce12a86166743b3339b711d8c5de77079a7b2ffd5c2743c46d2e780069f96
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.9
|
Security for ica-aroma-py 0.1.3
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.