vizo is now lab22
The VIZO command-line tool is now called lab22. This release of vizo installs
lab22 and keeps the vizo command working,
so an existing install moves over with one command:
pip install --upgrade vizo
From then on, vizo runs lab22: the same tool, with the same commands and
options. In a terminal it prints a one-line note saying so; scripts and jobs see
exactly what lab22 prints. Use the lab22 command from now on. A new install
needs only pip install lab22.
Nothing else has to change:
VIZO_API_KEYandVIZO_API_URLare still read whenLAB22_API_KEYandLAB22_API_URLare not set.- A download folder that vizo started keeps its
.vizo/folder, and lab22 resumes it as before. Do not rename.vizo/.
If you installed vizo with pipx, run pipx install lab22 instead, since pipx
does not expose a dependency's commands.
This package has no Python API. Code that imports vizo modules needs
vizo==0.0.5 or earlier, or the lab22 package.
The documentation is on the platform, at https://lab22.ai.
1 maintainer
Metadata
1 maintainer
Release files for vizo 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 | Actions |
|---|---|---|---|---|
| vizo-0.1.0.tar.gz | 2.9 kB | With provenance | Details for vizo-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| vizo-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for vizo-0.1.0-py3-none-any.whl |
Total release size: 6.1 kB
Release files / vizo-0.1.0.tar.gz
| Download URL | vizo-0.1.0.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
55316c879a1a1f24e4b325916d48c61f0e500489cea7f98bb53f8a5bbe32da82
|
|
BLAKE2b-256 checksum How to use checksums |
cb3a3f14a86f5ca61c789e4d34f0373811eed285b27d49822f19bf38b6154d0b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 28, 2026.
Transparency logRelease files / vizo-0.1.0-py3-none-any.whl
| Download URL | vizo-0.1.0-py3-none-any.whl |
|---|---|
| Size | 3.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f50508f06fe1ccfa1ae77267c762a66c53161a1b9426ba5951d7bfbe3db4845d
|
|
BLAKE2b-256 checksum How to use checksums |
e1b1561eeed48a85535d5e39b63b69d6256d4ffd9e54eccf00ff940cdd7c1fe8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 28, 2026.
Transparency logSecurity for vizo 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 vizo-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 28, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
