Metadata
1 maintainer
Release files for artificial-emotion 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 | |
|---|---|---|---|---|
| artificial_emotion-0.1.0.tar.gz | 4.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| artificial_emotion-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.6 kB
Release files / artificial_emotion-0.1.0.tar.gz
| Download URL | artificial_emotion-0.1.0.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9494a01b54fc2f9e006a777760b0bfa1a5a9b2864c6b669ad4af5eaa4497c811
|
|
BLAKE2b-256 checksum How to use checksums |
d0bc12285e8fb5949ca7ef460b5a3dfe682541f88326a9e484dd361d8401ead2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Release files / artificial_emotion-0.1.0-py3-none-any.whl
| Download URL | artificial_emotion-0.1.0-py3-none-any.whl |
|---|---|
| Size | 3.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
afe13b369116b0b47642da534b76ad1f00e416c6a428251a9cad9d762dc90f8f
|
|
BLAKE2b-256 checksum How to use checksums |
10fea6ab5d828125daf115b22d345bc1f2991340fdc8ec27b3ba058475ed705a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Security for artificial-emotion 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.
