Skip to main content

BANZAI Pipeline

This repo contains the data reduction package for Las Cumbres Observatory (LCO).

BANZAI stands for Beautiful Algorithms to Normalize Zillions of Astronomical Images.

See also https://banzai.readthedocs.io for more information.

Please cite the following DOI if you are using processed LCOGT data.

Zenodo DOI

We have recently implemented a neural network model to detect cosmic rays in ground based images. For more information pleas see our paper on arXiv. If possible please also cite Xu et al., 2021, arXiv:2106.14922.

Test Status Coverage Status Documentation Status

Installation

BANZAI uses uv for dependency management. Install uv first if you don’t have it:

curl -LsSf https://astral.sh/uv/install.sh | sh

Then install BANZAI and all dependencies including CPU-only PyTorch:

uv sync

All dependencies are managed automatically. A virtual environment is created in .venv in the project directory. Activate it before running any commands:

source .venv/bin/activate

Installing from PyPI

When installing BANZAI as a package (rather than from source), pass the pytorch-cpu index to avoid pulling the full CUDA-bundled PyTorch wheel from PyPI (~2GB):

uv pip install lco-banzai --extra-index-url https://download.pytorch.org/whl/cpu

The same flag applies when using pip instead of uv pip.

Usage

BANZAI has a variety of console entry points:

  • banzai_reduce_individual_frame: Process a single frame

  • banzai_reduce_directory: Process all frames in a directory

  • banzai_make_master_calibrations: Make a master calibration frame by stacking previously processed individual calibration frames.

  • banzai_automate_stack_calibrations: Start the scheduler that sets when to create master calibration frames

  • banzai_run_realtime_pipeline: Start the listener to detect and process incoming frames

  • banzai_mark_frame_as_good: Mark a calibration frame as good in the database

  • banzai_mark_frame_as_bad: Mark a calibration frame as bad in the database

  • banzai_update_db: Update the instrument table by querying the ConfigDB

  • banzai_add_instrument: Add an instrument to the database

  • banzai_add_site: Add a site to the database

  • banzai_add_super_calibration: Add a super calibration frame to the database

  • banzai_populate_bpms: Automatically populate the db with bpms from the archive

  • banzai_create_db: Initialize a database to be used when running the pipeline

  • banzai_create_local_db: Initialize a local database for site deployment, copying site/instrument info from a remote calibration database

You can see more about the parameters the commands take by adding a –help to any command of interest.

BANZAI can be deployed in two ways: an active pipeline that processes data as it arrives or a manual pipeline that is run from the command line.

For a runnable example of BANZAI in manual pipeline mode, refer to this jupyter notebook:

The main requirement to run BANZAI is that the database has been set up. BANZAI is database type agnostic as it uses SQLAlchemy. To create a new database to run BANZAI, run

from banzai.dbs import create_db
create_db('sqlite:///banzai-test.db')

This will create an sqlite3 database file in your current directory called banzai-test.db.

To run database migrations (e.g. after upgrading BANZAI), use the Alembic migration files bundled with the package:

DB_ADDRESS=postgresql://user:pass@host/dbname alembic -c $(python -c "import importlib.resources; print(importlib.resources.files('banzai').joinpath('alembic.ini'))") upgrade head

If you are not running this at LCO, you will have to add the instrument of interest to your database by running banzai_add_instrument before you can process any data.

By default, BANZAI requires a bad pixel mask. You can create one that BANZAI can use by using the tool here. To add a local bpm to the database, run

banzai_add_super_calibration path/to/bpm/file --db-address path/to/db

Generally, you have to reduce individual bias frames first by running banzai_reduce_individual_frame command. If the processing went well, you can mark them as good in the database using banzai_mark_frame_as_good. Once you have individually processed bias frames, you can create a master calibration using banzai_make_master_calibrations. This master calibration will then be available for future reductions of other observation types. Next, similarly reduce individual dark frames and then stack them to create a master dark frame. Then, the same for skyflats. At this point, you will be able to process science images using the banzai_reduce_individual_frame command.

To run the pipeline in its active mode, you need to setup a task queue and a filename queue. See the docker-compose-local.yml file for details on this setup.

Running Locally

To run BANZAI as a local pipeline, use docker-compose-local.yml. This is the recommended setup for development and for processing data independently of LCO’s site infrastructure.

Redis and RabbitMQ are managed separately via docker-compose-dependencies.yml so they can be left running across pipeline restarts. Start them first:

docker compose -f docker-compose-dependencies.yml up -d

Pipeline containers connect via the REDIS_URL and RABBITMQ_URL environment variables (defaulting to host.docker.internal). Site deployments can point these at existing infrastructure instead.

  1. Copy local-banzai-env.default to local-banzai-env and set your AUTH_TOKEN and DB_ADDRESS.

  2. Start the containers:

docker compose -f docker-compose-local.yml --env-file local-banzai-env up -d --build
  1. Queue images for processing. Raw files must be in $HOST_RAW_DIR:

uv run python scripts/queue_images.py $HOST_RAW_DIR

Processed output will be saved in $HOST_REDUCED_DIR.

Tests

Unit tests can be run using pytest. End-to-end tests are skipped by default, so to run only the unit tests locally run:

uv run pytest

The default pytest options exclude the e2e and e2e_site markers. The following markers are defined if you only want to run a subset of the tests:

  • e2e: End-to-end tests. Skip these if you only want to run unit tests.

  • master_bias: Only test making a master bias

  • master_dark: Only test making a master dark, assumes master bias frame already exists

  • master_flat: Only test making a master flat, assumes master bias and dark frames already exist

  • science_files: Only test processing science data, assumes master bias, dark, and flat frames already exist.

The end-to-end tests run on Jenkins at LCO automatically for every pull request.

To run the end-to-end tests locally, the easiest setup uses docker-compose. In the code directory run:

export DOCKER_IMG=banzai
docker build -t $DOCKER_IMG .
docker-compose up

After all of the containers are up, run

docker exec banzai-listener pytest --pyargs banzai.tests "-m e2e"

Site Deployment E2E Tests

The site E2E tests validate the full site deployment caching system, including PostgreSQL logical replication, calibration file caching, and Smartstack reduction and stacking. The site deployment is Smartstack-only: it does not run the realtime (fits_files → e91) pipeline. These tests are opt-in and are excluded from default pytest runs by the e2e_site marker.

They require Docker, Docker Compose, uv, and an LCO archive API token. The recommended entrypoint starts the shared Redis/RabbitMQ dependencies, then runs pytest. Pytest currently starts and tears down the publication database and site deployment containers.

To run the site E2E tests:

# Copy and configure the environment file
cp banzai/tests/site_e2e/site_e2e.env.template banzai/tests/site_e2e/site_e2e.env
# Edit site_e2e.env and add your AUTH_TOKEN

# Run the tests
scripts/run_site_e2e.sh

For advanced debugging, you can run pytest directly after starting Redis/RabbitMQ yourself:

docker compose -f docker-compose-dependencies.yml up -d
uv run pytest -m e2e_site banzai/tests/site_e2e/test_site_e2e.py -v -s

The following markers can be used to run subsets of the site E2E tests:

  • e2e_site: All site deployment tests

  • e2e_site_startup: Publication DB and site deployment startup tests

  • e2e_site_cache: Cache synchronization tests

  • e2e_site_reduction: Smartstack reduction and stacking tests

Publish Changes to PyPI

  1. Update Change log in CHANGES.md.

  2. uv version --bump [major/minor/patch] # use UV to bump version, sync, and update lock file.

  3. Commit changes and merge into main.

  4. git checkout main # checkout main branch (be sure to pull/push as need to be in sync)

  5. git tag -m '[message]' x.x.x # tag main to the new version

  6. git push --tags # Push tags up to github

  7. Go to tags on github, select new tag and generate a release.

  8. Publish release.

If there are problems, check the recent github action named after the new tag for more information. Packages should be published to https://pypi.org/project/lco-banzai/.

License

This project is Copyright (c) Las Cumbres Observatory and licensed under the terms of GPLv3. See the LICENSE file for more information.

Support

Create an issue

Powered by Astropy Badge

Metadata

Release files for lco-banzai 1.43.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for lco-banzai 1.43.0
File Size Uploaded Provenance Actions
lco_banzai-1.43.0.tar.gz 1.1 MB With provenance Details for lco_banzai-1.43.0.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for lco-banzai 1.43.0
File Actions
lco_banzai-1.43.0-cp315-cp315t-musllinux_1_2_x86_64.whl CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ x86-64 Details for lco_banzai-1.43.0-cp315-cp315t-musllinux_1_2_x86_64.whl
lco_banzai-1.43.0-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.15 CPython 3.15 free-threading Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for lco_banzai-1.43.0-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
lco_banzai-1.43.0-cp315-cp315-musllinux_1_2_x86_64.whl CPython 3.15 CPython 3.15 Linux musl 1.2+ x86-64 Details for lco_banzai-1.43.0-cp315-cp315-musllinux_1_2_x86_64.whl
lco_banzai-1.43.0-cp315-cp315-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.15 CPython 3.15 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for lco_banzai-1.43.0-cp315-cp315-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
lco_banzai-1.43.0-cp314-cp314t-musllinux_1_2_x86_64.whl CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-64 Details for lco_banzai-1.43.0-cp314-cp314t-musllinux_1_2_x86_64.whl
lco_banzai-1.43.0-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details for lco_banzai-1.43.0-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
lco_banzai-1.43.0-cp314-cp314-musllinux_1_2_x86_64.whl CPython 3.14 CPython 3.14 Linux musl 1.2+ x86-64 Details for lco_banzai-1.43.0-cp314-cp314-musllinux_1_2_x86_64.whl
lco_banzai-1.43.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for lco_banzai-1.43.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
lco_banzai-1.43.0-cp313-cp313-musllinux_1_2_x86_64.whl CPython 3.13 CPython 3.13 Linux musl 1.2+ x86-64 Details for lco_banzai-1.43.0-cp313-cp313-musllinux_1_2_x86_64.whl
lco_banzai-1.43.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for lco_banzai-1.43.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
lco_banzai-1.43.0-cp312-cp312-musllinux_1_2_x86_64.whl CPython 3.12 CPython 3.12 Linux musl 1.2+ x86-64 Details for lco_banzai-1.43.0-cp312-cp312-musllinux_1_2_x86_64.whl
lco_banzai-1.43.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for lco_banzai-1.43.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
lco_banzai-1.43.0-cp311-cp311-musllinux_1_2_x86_64.whl CPython 3.11 CPython 3.11 Linux musl 1.2+ x86-64 Details for lco_banzai-1.43.0-cp311-cp311-musllinux_1_2_x86_64.whl
lco_banzai-1.43.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for lco_banzai-1.43.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Total release size: 28.6 MB

Release files / lco_banzai-1.43.0.tar.gz

Download URL lco_banzai-1.43.0.tar.gz
Size 1.1 MB
Tags Source
SHA-256 checksum
How to use checksums
db675ceee6e518c4975d619baa943e2bb6712cbef72253d81f4761c4cc9286ce
BLAKE2b-256 checksum
How to use checksums
fcdda7eee3a5e31a264d994c42d8594962ee597e98318d57f592c19d89e58813
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 Nov 18, 2026.

Transparency log

Release files / lco_banzai-1.43.0-cp315-cp315t-musllinux_1_2_x86_64.whl

Download URL lco_banzai-1.43.0-cp315-cp315t-musllinux_1_2_x86_64.whl
Size 2.0 MB
Tags CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
6565524401dc2c069fe1227966d3ee6faa250a69a9b80ff622f442bca24e7bbb
BLAKE2b-256 checksum
How to use checksums
d433523f4a87c78e2cce5aa933c4e1942cc47ccff946f27e46ea14584f429409
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 Nov 18, 2026.

Transparency log

Release files / lco_banzai-1.43.0-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL lco_banzai-1.43.0-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.15 CPython 3.15 free-threading Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
1c8875dca942afc094172afcc2f80c8f1a5123113cecd83f1e99eb4f9a1cfbf3
BLAKE2b-256 checksum
How to use checksums
9cf01e4163759190b94f9de075779438b539dd573ea4cb27e7fd0a171f48fce9
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 Nov 18, 2026.

Transparency log

Release files / lco_banzai-1.43.0-cp315-cp315-musllinux_1_2_x86_64.whl

Download URL lco_banzai-1.43.0-cp315-cp315-musllinux_1_2_x86_64.whl
Size 2.0 MB
Tags CPython 3.15 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
121a421762238638fb8e2fe6239a950ed60bd2baa037d8a2e22d67ec0a599feb
BLAKE2b-256 checksum
How to use checksums
e0047f22ce5529469ff1c8b527d6ba1e23126801488fe14ce15056f3079cffa8
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 Nov 18, 2026.

Transparency log

Release files / lco_banzai-1.43.0-cp315-cp315-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL lco_banzai-1.43.0-cp315-cp315-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.15 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
10c5c259823e4fdf06f873d5446dcb61f0fa0b6cef2c66a296f52a6b80723fc2
BLAKE2b-256 checksum
How to use checksums
1e73783327140904153b3219805890fd364e342b76a63fb6e345af8c7a2fb209
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 Nov 18, 2026.

Transparency log

Release files / lco_banzai-1.43.0-cp314-cp314t-musllinux_1_2_x86_64.whl

Download URL lco_banzai-1.43.0-cp314-cp314t-musllinux_1_2_x86_64.whl
Size 2.0 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
6f92a698016c01a7646dec667eda8cc5905540feba68bdd6b905ecc091522507
BLAKE2b-256 checksum
How to use checksums
8042fe708a3b1b63c926ff72fce59b7779749425e6b567cfb3548c275fb8c6cc
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 Nov 18, 2026.

Transparency log

Release files / lco_banzai-1.43.0-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL lco_banzai-1.43.0-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
fed3b2a716b6d5b8a6a347e12147f786a27dd90870a04412447427a743d6c629
BLAKE2b-256 checksum
How to use checksums
f903bad16bdeb082a718e5e240ad0bbc2d05ba76400c6bf7a28472208b00abb6
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 Nov 18, 2026.

Transparency log

Release files / lco_banzai-1.43.0-cp314-cp314-musllinux_1_2_x86_64.whl

Download URL lco_banzai-1.43.0-cp314-cp314-musllinux_1_2_x86_64.whl
Size 2.0 MB
Tags CPython 3.14 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
af4ea21a38889fbd42b027b12d780add5efc02ff4ae4b355427f7b56a7552a1d
BLAKE2b-256 checksum
How to use checksums
9f378fe75d692476c1f65580295032c30293233071b2fb21eefc18050fc46422
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 Nov 18, 2026.

Transparency log

Release files / lco_banzai-1.43.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL lco_banzai-1.43.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.14 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
0cd593ceb0ddf5b8fd37f227ae464e70c7fa3272e6b28fd48ff483d17e3bdebd
BLAKE2b-256 checksum
How to use checksums
29f21a84c4fecd0006bb2d6ff2ff691c1be954af8c3cdd4d798e974c900c336a
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 Nov 18, 2026.

Transparency log

Release files / lco_banzai-1.43.0-cp313-cp313-musllinux_1_2_x86_64.whl

Download URL lco_banzai-1.43.0-cp313-cp313-musllinux_1_2_x86_64.whl
Size 2.0 MB
Tags CPython 3.13 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
c007f08059655dc3899c42174867db7ab9d4e5db4b16ebd6340135d337a1a12d
BLAKE2b-256 checksum
How to use checksums
6cdee8d9c941b4caa184b90e0b5d3b18d2bb9e487b6c64e5a108ea0e74815768
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 Nov 18, 2026.

Transparency log

Release files / lco_banzai-1.43.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL lco_banzai-1.43.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
30b71cd1a2a2d7ca97706319295feb17762add811d85af756ae4ddf4cfa6628e
BLAKE2b-256 checksum
How to use checksums
8512cb4ac62a110ec5631a047ec9b0222b8a81887ad81c1164af50addbba264f
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 Nov 18, 2026.

Transparency log

Release files / lco_banzai-1.43.0-cp312-cp312-musllinux_1_2_x86_64.whl

Download URL lco_banzai-1.43.0-cp312-cp312-musllinux_1_2_x86_64.whl
Size 2.0 MB
Tags CPython 3.12 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
34652b634ff1ca9f84a2e71594bcd19681ec6f6ed2a62fc900d4f717c7d71888
BLAKE2b-256 checksum
How to use checksums
8b64fcf28da9c2b667b6d5536aaa2745eb7aebc6ed6c60afa1c6f91a49246f00
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 Nov 18, 2026.

Transparency log

Release files / lco_banzai-1.43.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL lco_banzai-1.43.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
279f84cd7ace82e359f19565140673b573e165903538d9dc548d2859811afc2a
BLAKE2b-256 checksum
How to use checksums
7be0a24403ce8d76a6dd7eb5408099abec35f71b6b4456a49aa81cc65dfb4748
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 Nov 18, 2026.

Transparency log

Release files / lco_banzai-1.43.0-cp311-cp311-musllinux_1_2_x86_64.whl

Download URL lco_banzai-1.43.0-cp311-cp311-musllinux_1_2_x86_64.whl
Size 1.8 MB
Tags CPython 3.11 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
49537dc132a44f297e333265dc5b4c7d3cec32e3381871b475328851f117e960
BLAKE2b-256 checksum
How to use checksums
70b1f78d984a7c2c740a84e99bbfbc86096640f12846c2497f5206101911f625
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 Nov 18, 2026.

Transparency log

Release files / lco_banzai-1.43.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL lco_banzai-1.43.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 1.8 MB
Tags CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
2abf178521266c85240aca1565e4018db4815808a1d597138a43248399e86f10
BLAKE2b-256 checksum
How to use checksums
616a8f7ca67a4e046aea230880c509a78e60dd4f52fa4db5f603c6ed839842e5
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 Nov 18, 2026.

Transparency log

Security for lco-banzai 1.43.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 15 files in this release have been uploaded with provenance metadata.

Select from 15 files

Attestation for lco_banzai-1.43.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 Nov 18, 2026.

Transparency log

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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page