The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for aroma-py 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 | |
|---|---|---|---|---|
| aroma-py-0.0.1.tar.gz | 3.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aroma_py-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.1 kB
Release files / aroma-py-0.0.1.tar.gz
| Download URL | aroma-py-0.0.1.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
220d9a0ca11a11f6fefaba1153faa9d73243a4944c486ab77a91d8456317a9b3
|
|
BLAKE2b-256 checksum How to use checksums |
3068773ab8e9f6fac1a9366846d23f2e7998e24bfa57c6b1598d3903797d3570
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.4
|
Release files / aroma_py-0.0.1-py3-none-any.whl
| Download URL | aroma_py-0.0.1-py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bb845ae41ea933b8c5a6f04f477575828922d9e6235a91a74d5f5d9ea0b52e68
|
|
BLAKE2b-256 checksum How to use checksums |
7bde0f6ec7788156be4eace417b0bf5c78aa1a910fadeb869acc484a3db749ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.4
|
Security for aroma-py 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.
