recc-vp
Recc Visual Programming
License
See the LICENSE file for details. In summary, recc-vp is licensed under the MIT license.
Metadata
Release files for recc-vp 2.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| recc_vp-2.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Release files / recc_vp-2.0.3-py3-none-any.whl
| Download URL | recc_vp-2.0.3-py3-none-any.whl |
|---|---|
| Size | 2.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ac954dac064f6aef4a9b47e0b20d6762fa14bc06a5bfbfa2ad0a7b2b8dab1861
|
|
BLAKE2b-256 checksum How to use checksums |
a8f158839e05ae20042584bb64feb74add71149856ff53dc0a2c0fcdacdb9564
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.11
|
Security for recc-vp 2.0.3
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.