1 maintainer
Metadata
1 maintainer
Release files for anywave-plugin-api 1.0.2
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.0.2.tar.gz | 19.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| anywave_plugin_api-1.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 41.9 kB
Release files / anywave_plugin_api-1.0.2.tar.gz
| Download URL | anywave_plugin_api-1.0.2.tar.gz |
|---|---|
| Size | 19.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
49592aa5972180c9cd155d63cec754cd8d3eca7350620f58ebb674ffed4b9ecf
|
|
BLAKE2b-256 checksum How to use checksums |
db86b10b7f136b03329359d5cb29789e8d83909abd0a59563e3e2137d02d8d1a
|
| 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.0.2-py3-none-any.whl
| Download URL | anywave_plugin_api-1.0.2-py3-none-any.whl |
|---|---|
| Size | 22.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b8688c9ab55e6fabcffa89f933adfd2a693f1b5e3c396b600a16990dc384e27d
|
|
BLAKE2b-256 checksum How to use checksums |
9aa73cd31ddf39179ff1032af4230f10598460f5f5cc22e60a528b11db1fcf80
|
| 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.0.2
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.
