The author of this package has not provided a project description
Metadata
Release files for aworda 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 | |
|---|---|---|---|---|
| aworda-0.1.0.tar.gz | 797 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aworda-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.8 kB
Release files / aworda-0.1.0.tar.gz
| Download URL | aworda-0.1.0.tar.gz |
|---|---|
| Size | 797 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7585a39b536ad63ce90b2226c2c0717e09b39530155156d6c14525d7fa744e53
|
|
BLAKE2b-256 checksum How to use checksums |
850e4ef368b520ea107249b9e9da6ad2d5ff196da5a37f2331e4a5e9dbef28c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.12 CPython/3.8.10 Linux/5.4.0-90-generic
|
Release files / aworda-0.1.0-py3-none-any.whl
| Download URL | aworda-0.1.0-py3-none-any.whl |
|---|---|
| Size | 982 Bytes |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c3f5cfcfc8d98ae17dc365c3aed82d3497aaef4b733522dcf8d4756eefca6a8d
|
|
BLAKE2b-256 checksum How to use checksums |
84e4487766a98ece7322bb669cd41a972a631f691bde3a866069675478fc39c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.12 CPython/3.8.10 Linux/5.4.0-90-generic
|
Security for aworda 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.