recc-co
Recc Container Orchestration
License
See the LICENSE file for details. In summary, recc-co is licensed under the MIT license.
Metadata
Release files for recc-co 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_co-2.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Release files / recc_co-2.0.3-py3-none-any.whl
| Download URL | recc_co-2.0.3-py3-none-any.whl |
|---|---|
| Size | 2.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b207f42cdba49dbb517877d5fae7a80e5d339f3fab727f8b194c27dea9040811
|
|
BLAKE2b-256 checksum How to use checksums |
dd371da3b77b44c8d9e332c46d2b4c4f8e5fde93f6652f47e171946426a0d223
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.11
|
Security for recc-co 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.