2 maintainers
Metadata
2 maintainers
Release files for ocd-colt 0.0.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 | |
|---|---|---|---|---|
| ocd_colt-0.0.0.tar.gz | 832 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ocd_colt-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.2 kB
Release files / ocd_colt-0.0.0.tar.gz
| Download URL | ocd_colt-0.0.0.tar.gz |
|---|---|
| Size | 832 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0fe010bcdda670137ffb30baa588a25b85a395d7cf71082f59158194ebdce507
|
|
BLAKE2b-256 checksum How to use checksums |
b9e29581216ad18c45536cb99829bf2a36974c802c88d9295fc373e35c699fdc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / ocd_colt-0.0.0-py3-none-any.whl
| Download URL | ocd_colt-0.0.0-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1843d7786c720a96ece168335f3bc624229acb76a501b9067a704184e669a790
|
|
BLAKE2b-256 checksum How to use checksums |
a2fe24041294504386167f740fc6d36752d889509ff105375de318a1e83d0f68
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for ocd-colt 0.0.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.
