afolio
Store named scientific arrays with optional JSON records and explicit SHA-256 integrity checks. The local storage uses standard Zarr v3; arrays remain readable without afolio. Python 3.13 or newer is required.
Released under the MIT License.
uv sync --all-extras --managed-python
uv run python examples/local_dataset.py
For another uv project in a sibling directory, add this checkout with
uv add ../afolio --extra tiff --extra ome (adjust the checkout path as needed).
The package has not been published to PyPI.
Read the getting started guide, API reference, disk format, and OME-Zarr and TIFF guide. Read-only SFTP access is described in the remote guide. Development decisions and progress live in memo/. See development setup for Git hooks and verification commands.
The current implementation supports local datasets, stage records, integrity checks, TIFF/OME-TIFF exports, optional OME-Zarr 0.5 image reading/writing, and read-only SFTP access with connection reuse, bounded memory/disk caching and ROI prefetch. Trusted signatures, remote writes and pyramid generation are planned extensions.
1 maintainer
Metadata
1 maintainer
Release files for afolio 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 | |
|---|---|---|---|---|
| afolio-0.1.0.tar.gz | 15.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| afolio-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 35.9 kB
Release files / afolio-0.1.0.tar.gz
| Download URL | afolio-0.1.0.tar.gz |
|---|---|
| Size | 15.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
03ac3de9bb489c92b93babc0b27ae110a2db2f1529990772dfdee663724ee36d
|
|
BLAKE2b-256 checksum How to use checksums |
f3077c5a1b63f9d106107aeb16886a18a86219b73357bbc972ffa4009360fc9b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency logRelease files / afolio-0.1.0-py3-none-any.whl
| Download URL | afolio-0.1.0-py3-none-any.whl |
|---|---|
| Size | 20.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
872600d57d420a1c7ed26838bac845779664a6f5a0407437e2f6ac5f13d8bda0
|
|
BLAKE2b-256 checksum How to use checksums |
85d43861f1d893f8be3a9cb949cdef0ae88ebbdc543ae675e0d19dd96796a3e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency logSecurity for afolio 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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for afolio-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency logA 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.
