The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for imglib2 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 | |
|---|---|---|---|---|
| imglib2-0.1.0.tar.gz | 1.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| imglib2-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.0 kB
Release files / imglib2-0.1.0.tar.gz
| Download URL | imglib2-0.1.0.tar.gz |
|---|---|
| Size | 1.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f8d8b5380d270e9e902df4e92466e853fcc16a4b3c68b308ad7ca3f5e0173053
|
|
BLAKE2b-256 checksum How to use checksums |
b50d3ea8000aac3e607cd6350a3f91f14c6c245bbd4dc1887c96eb45258bc432
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.10
|
Release files / imglib2-0.1.0-py3-none-any.whl
| Download URL | imglib2-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a08ee347ec58593627285cb246ab8eae277cab8c87bcd01036e2c08b5107f343
|
|
BLAKE2b-256 checksum How to use checksums |
605bcbb4b755ad8126cd679a418252ac453b2f9a4d792a14d1bb5e81cb5b9e58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.10
|
Security for imglib2 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.
