The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for cribrum 0.1.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 | |
|---|---|---|---|---|
| cribrum-0.1.0.tar.gz | 555 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cribrum-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.6 kB
Release files / cribrum-0.1.0.tar.gz
| Download URL | cribrum-0.1.0.tar.gz |
|---|---|
| Size | 555 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
31429ba9153965de7f64f4c5a342d96fede0afbf9717438a2a7c250645abd571
|
|
BLAKE2b-256 checksum How to use checksums |
4c99114c3f5115effc04767cc18689231abd5fd6688dda473e73c6e5d652f39d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Release files / cribrum-0.1.0-py3-none-any.whl
| Download URL | cribrum-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0d16bba58bbd53d3504f45c2b96e24d5c364c14566c41ffc8c57f66936408d8b
|
|
BLAKE2b-256 checksum How to use checksums |
27becc08a3d47780422b8c3044076f98a4622b56add1a926b0048a0ff26e8905
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for cribrum 0.1.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.
