1 maintainer
Metadata
1 maintainer
Release files for omu-chatprovider 0.10.12
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 | |
|---|---|---|---|---|
| omu_chatprovider-0.10.12.tar.gz | 6.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| omu_chatprovider-0.10.12-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.5 kB
Release files / omu_chatprovider-0.10.12.tar.gz
| Download URL | omu_chatprovider-0.10.12.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0bf95f66e872ebb385c36e857a22e41f2db48843c028137e01c5a7497fbafbc8
|
|
BLAKE2b-256 checksum How to use checksums |
68ca46ed8c5ba584dcd417f06561be5883bcdcff44cbe79cca6bf3a690e13644
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
Release files / omu_chatprovider-0.10.12-py3-none-any.whl
| Download URL | omu_chatprovider-0.10.12-py3-none-any.whl |
|---|---|
| Size | 8.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
756d32bf636da00e84eae3382051917a3b926acf83ed69a66d58edc345f19aa8
|
|
BLAKE2b-256 checksum How to use checksums |
ac3f39c4cc8d2e28747c80475263bf71cfe72d0455a5b96b986912bd348fca42
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
Security for omu-chatprovider 0.10.12
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.
