1 maintainer
Metadata
1 maintainer
Release files for anywave-plugin-api 1.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 | |
|---|---|---|---|---|
| anywave_plugin_api-1.1.0.tar.gz | 20.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| anywave_plugin_api-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 43.9 kB
Release files / anywave_plugin_api-1.1.0.tar.gz
| Download URL | anywave_plugin_api-1.1.0.tar.gz |
|---|---|
| Size | 20.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ccfdb3ca64e49964d56fbefec4abd4537d573e4222c0394597c01574ae40a1e5
|
|
BLAKE2b-256 checksum How to use checksums |
fcc8b7756bd9c8d9a11024781494b113862a41f074a967a59d7195f15eaf939b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Release files / anywave_plugin_api-1.1.0-py3-none-any.whl
| Download URL | anywave_plugin_api-1.1.0-py3-none-any.whl |
|---|---|
| Size | 23.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dd017140e59e7659247d10daf83432f96862f38afcb7b860d12269dc3c112d3b
|
|
BLAKE2b-256 checksum How to use checksums |
7d844e0fef7f3973c48efeb149bb5d92098fe834cac23601f8db94fa4c2e3f64
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Security for anywave-plugin-api 1.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.
