Metadata
1 maintainer
Release files for sulci-cache 0.0.1
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 | |
|---|---|---|---|---|
| sulci_cache-0.0.1.tar.gz | 1.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sulci_cache-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.5 kB
Release files / sulci_cache-0.0.1.tar.gz
| Download URL | sulci_cache-0.0.1.tar.gz |
|---|---|
| Size | 1.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
83d3c21f5731f49acc6bc2461e959640dc253c8d0782156898c70b516b8a8f39
|
|
BLAKE2b-256 checksum How to use checksums |
a3d1677d2915519cfb2d9af5afb0892b1a1366169da11f4c1121042dd7e5ea9a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.2
|
Release files / sulci_cache-0.0.1-py3-none-any.whl
| Download URL | sulci_cache-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fec676811bc37d50d3ca9c2506310fbb8e41baa71d1100f1dfc255009a059a45
|
|
BLAKE2b-256 checksum How to use checksums |
3385bd5be1b748de2e3758e7d4488db36f3b772283509fdbd585a02b560100cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.2
|
Security for sulci-cache 0.0.1
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.
