The author of this package has not provided a project description
Metadata
Release files for ica-aroma-py 0.1.4
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.4.tar.gz | 73.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ica_aroma_py-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 146.7 kB
Release files / ica_aroma_py-0.1.4.tar.gz
| Download URL | ica_aroma_py-0.1.4.tar.gz |
|---|---|
| Size | 73.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dee2e919854555cdb241c7d2ae90a936ac8fff4bb7034e6bc750b992e059674b
|
|
BLAKE2b-256 checksum How to use checksums |
8373bd5a4c6ca91702416bf97c7978e9495c39a501a201270093ce85b36ee7e2
|
| 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.4-py3-none-any.whl
| Download URL | ica_aroma_py-0.1.4-py3-none-any.whl |
|---|---|
| Size | 73.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
098fe7eb4ec424e4abfc7b4d5e4139272e3e411fc006171c1346abcc54759dd7
|
|
BLAKE2b-256 checksum How to use checksums |
d71262fe2f0ea85b8be4c5259724ca10c100e71f0576b84020d2fafa23fae8e4
|
| 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.4
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.