cvpa
Computer Vision Player Agent
License
See the LICENSE file for details. In summary, osom-api is licensed under the MIT license.
Metadata
Release files for cvpa 0.2.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 | |
|---|---|---|---|---|
| cvpa-0.2.0.tar.gz | 66.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cvpa-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 121.2 kB
Release files / cvpa-0.2.0.tar.gz
| Download URL | cvpa-0.2.0.tar.gz |
|---|---|
| Size | 66.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2c485d82e7669958ec916489c2a4a319664e5efd5e51da2cc47ae8fdeed72163
|
|
BLAKE2b-256 checksum How to use checksums |
f8011e7641617fb4110229823b4f42b5a34b5dc6327c182acd995acdbc7d9744
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / cvpa-0.2.0-py3-none-any.whl
| Download URL | cvpa-0.2.0-py3-none-any.whl |
|---|---|
| Size | 55.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d73a49ada074ba3317c012c6825742a4993b17041a8bf10518d270cff3dd6dc4
|
|
BLAKE2b-256 checksum How to use checksums |
2b7a27128ee8bc545afec6589f976a1b53d1b7902264af0cf9f8cb363ecdde4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for cvpa 0.2.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.