This release is a pre-release and may not be stable for production use.
The author of this package has not provided a project description
Metadata
Release files for colars 0.1.0b0
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 | |
|---|---|---|---|---|
| colars-0.1.0b0.tar.gz | 1.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| colars-0.1.0b0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.4 kB
Release files / colars-0.1.0b0.tar.gz
| Download URL | colars-0.1.0b0.tar.gz |
|---|---|
| Size | 1.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b8fc158693cdeffd94b4c87ce38dde94f4c5c01e9c263d6c30215208f4939704
|
|
BLAKE2b-256 checksum How to use checksums |
e8195df784334bd01ee9ca35e24083847229217d40c898d236b9736692c194a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.12
|
Release files / colars-0.1.0b0-py3-none-any.whl
| Download URL | colars-0.1.0b0-py3-none-any.whl |
|---|---|
| Size | 1.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
33a48346ee91b732afe04452f0178f5566409374bdec3ad40ea31eb41ba8300d
|
|
BLAKE2b-256 checksum How to use checksums |
90140551cbe9547e0995a435a3ed20a579174685ed7a4b7d14523b52b6696f1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.12
|
Security for colars 0.1.0b0
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.