prot-struct-viz
Render a protein structure as a self-contained static HTML file using Mol*, with residues colored, labeled, and styled from a CSV. Everything the view needs — coordinates, colors, tooltips, labels — is embedded in the one file, so it can be dropped on GitHub Pages with no backend.
- Documentation: https://jbloomlab.github.io/prot-struct-viz/
- Live example: https://jbloomlab.github.io/prot-struct-viz/examples/
Install
pip install prot-struct-viz
Quick start
Write a CSV of the residues you want to say something about, and a spec file naming the structure, where the HTML goes, and one or more views of it. Then:
prot-struct-viz spec.yaml
That writes the page, plus a report on any disagreement between the CSV and the structure. One spec can hold several named views — different colorings, labels, representations, or heteroatoms — and the page gets a selector that switches between them without moving the camera. The URL tracks the selector, so a link can point at one particular view.
The quick start shows both files in full; the documentation covers every spec key, the CSV columns, and what a reader of the output can click.
Development
python3 -m venv .venv && source .venv/bin/activate
pip install -e ".[dev,docs]"
scripts/check.sh # pytest + ruff + black
scripts/build_examples.sh # render examples/*/spec.yaml into examples/output/
scripts/build_docs.sh # mkdocs build --strict
Documentation lives in docs/, which is the single source — this README is a front door,
not a second copy. Conventions, and the checks to run after changing anything that affects
rendering, are in CLAUDE.md.
Releasing
Releases are tag-driven and publish to PyPI through
trusted publishing, so no API token is
stored in the repo. The one-time PyPI setup and the per-release recipe are documented at
the top of .github/workflows/release.yml. In short:
# 1. Bump `version` in pyproject.toml and roll CHANGELOG's [Unreleased] into it.
git commit -am "release vX.Y.Z"
git tag vX.Y.Z
git push && git push --tags
The workflow verifies the tag matches pyproject.toml before anything reaches PyPI.
Metadata
Release files for prot-struct-viz 0.3.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 | |
|---|---|---|---|---|
| prot_struct_viz-0.3.0.tar.gz | 216.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| prot_struct_viz-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 261.7 kB
Release files / prot_struct_viz-0.3.0.tar.gz
| Download URL | prot_struct_viz-0.3.0.tar.gz |
|---|---|
| Size | 216.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
07a1e745b7f322612cf181297de50bd3fc92decb58d479b923b093a9b1b4f192
|
|
BLAKE2b-256 checksum How to use checksums |
ed88f817b1c8a27f8102044200d487ffae9765a5fe2f8f969be74a8bc2295e6e
|
| 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 Sep 2, 2026.
Transparency logRelease files / prot_struct_viz-0.3.0-py3-none-any.whl
| Download URL | prot_struct_viz-0.3.0-py3-none-any.whl |
|---|---|
| Size | 45.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cf99d9b9ad74350f7b8c522f007cc47bb61d83dc268b347ee6b5375f03c0caba
|
|
BLAKE2b-256 checksum How to use checksums |
b03a00aee681baca375e7d64d2fec6f7052b199c8ae59bbe48c48ccf8659ab91
|
| 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 Sep 2, 2026.
Transparency logSecurity for prot-struct-viz 0.3.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 prot_struct_viz-0.3.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 Sep 2, 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.