binderqc
Quality control and tag-site scoring for designed protein binders.
Install
pip install binderqc
Python 3.10+. Pulls in biotite, numpy, and pandas. For development from
source: pip install -e ".[test]".
Usage
binderqc --binder-chains A --target-chains B --out out.csv complex.cif some_dir/
from binderqc import score_structure
rows = score_structure("complex.pdb", binder_chains=["A"], target_chains=["B"])
Inputs are PDB/CIF files, globs, or directories. Leave --binder-chains off to
guess the binder as the shortest chain (20-250 aa, printed for each file);
--target-chains defaults to the remaining chains.
| flag | default | meaning |
|---|---|---|
--binder-chains |
auto-guess | comma-separated binder chain ids |
--target-chains |
all non-binder | comma-separated target chain ids |
--interface-cutoff |
5.0 |
heavy-atom contact distance (Å) |
--exposure-cutoff |
0.25 |
relSASA below which a terminus is buried |
--out |
binderqc.csv |
output CSV path |
-j, --jobs |
1 |
worker processes to score a batch of files in parallel |
--fasta |
off | also write the QC-passing binders to this FASTA |
Scoring is CPU-only (no folding, no GPU, no network). Files in a batch are
independent, so -j scales near-linearly across cores for large directories.
Example output for the bundled LCB1 minibinder (a few of the columns):
| recommended_tag | binder_bsa | epitope_planarity | epitope_aromatic_n | pi | qc_pass |
|---|---|---|---|---|---|
| C | 1021.4 | 3.21 | 11 | 4.17 | True |
Its warnings field reads "both termini ~equidistant from interface (ambiguous)",
a tag-site advisory, so qc_pass stays True.
What it reports
Per binder chain:
- Interface: buried surface area, interface residue count, hydrogen-bond and salt-bridge counts, and a contact-packing density (a lightweight proxy for contact molecular surface).
- Pose: approach angle (end-on vs. lying across the surface).
- Grippability: epitope planarity, hydrophobic fraction, aromatic anchors, and a
SASA-aware glyco-occlusion check (
epitope_glyco_occluded,epitope_glyco_sites) — N-glycosylation sequons (N-X-[S/T]) that are exposed on the free target and sit at/near the epitope, so an installed glycan would mask an otherwise grippable patch.grippability_consensus(row, iara_score)optionally cross-checks this physical read against a learned target-side score (e.g. an IARA epitope mean, computed by the caller so binderqc stays dependency-clean), returninggrippable/flat/disagree; pass--iara-scoreon the CLI to add it as a column. - Tag site: recommended terminus (N/C) and the numbers behind it: relative SASA, CA-CA distance to the paratope, orientation, and a terminal cysteine's SG SASA.
- Developability: two complementary aggregation scores — an SAP-style spatial
aggregation score (
sap_score/sap_total) and an Aggrescan3D score (a3d_score/a3d_total_positive, a faithful pure-Python port of Aggrescan3D 1.0.2's a3v scale + algorithm; Pearson r≈0.92 vs the reference tool) — plus the ProtParam instability index (Guruprasad 1990), GRAVY, pI, MW, ε₂₈₀, and sequence liabilities. Liabilities cover deamidation (N-[G/S/T]), Asp isomerization (D-[G/S/T/D/H]), unpaired cysteines, N-glycosylation sequons, and — SASA-aware, so only surface-exposed residues count — Met/Trp oxidation hotspots.
A warnings column flags problems (small, flat, anchorless, or glyco-occluded
interfaces; buried, ambiguous, or interface-facing tag sites; hydrophobic sequences). qc_pass is
true when there are no quality warnings (tag-site advisories like an ambiguous
terminus do not count), and --fasta writes those binders.
Full column list
pdb, binder_chain, target_chains, n_interface_res, binder_bsa, n_hbonds, n_salt_bridges, interface_packing, approach_angle, epitope_planarity, epitope_hydrophobic_frac, epitope_aromatic_n, epitope_glyco_occluded, epitope_glyco_sites, nterm_resnum, nterm_resname, nterm_relsasa, nterm_dist_to_interface, nterm_orientation, nterm_sg_sasa, cterm_resnum, cterm_resname, cterm_relsasa, cterm_dist_to_interface, cterm_orientation, cterm_sg_sasa, recommended_tag, mw, gravy, pi, instability_index, ext_coeff_280, sap_score, sap_total, a3d_score, a3d_total_positive, sequence_liabilities, warnings, qc_pass, binder_sequence
Tests
pip install -e ".[test]"
pytest
Runs against a bundled example, PDB 7JZU (the LCB1 minibinder on the SARS-CoV-2 RBD). LCB1 comes from Cao et al. (2020), which frames the problem binderqc targets: the bottleneck is selecting good binders, not designing them.
"…not in the de novo design of proteins with shape and chemical complementarity to the target surface, but in recognizing the best candidates."
In that work LCB1 buries ~1,000 Ų and forms "multiple hydrogen bonds and salt bridges … consistent with the subnanomolar affinities". binderqc on 7JZU agrees: 1021 Ų buried area (Cao reports ~1,000 Ų), plus 2 salt bridges and 17 interface polar contacts. See Cao et al., De novo design of picomolar SARS-CoV-2 miniprotein inhibitors, Science 370, 426-431 (2020), doi:10.1126/science.abd9909.
tests/pisa_correctness.py is a separate script (not part of the unit tests). It
downloads 18 public complexes from RCSB and PDBePISA and checks the interface area
against PISA (r ~ 1.0, about 1% median error):
pip install -e ".[validation]"
python tests/pisa_correctness.py
Figures
The complex in the banner is a real render, not a drawing:
docs/render_structure.py draws a cartoon under a translucent molecular surface
(binder blue, target grey) from actual coordinates, using 3Dmol.js in headless
Chromium. It works on any PDB/CIF, so it is reusable for your own figures:
pip install -e ".[docs]" && python -m playwright install chromium
python docs/render_structure.py complex.pdb A B out.png # structure, binder chain, target chain, output
License
MIT
Metadata
Release files for binderqc 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 | |
|---|---|---|---|
| binderqc-0.3.0.tar.gz | 2.8 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| binderqc-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.8 MB
Release files / binderqc-0.3.0.tar.gz
| Download URL | binderqc-0.3.0.tar.gz |
|---|---|
| Size | 2.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6136a67eb0593dd6e7e5e5078e7050acb5f0b499a2729a8994bbea94e6565068
|
|
BLAKE2b-256 checksum How to use checksums |
2c8a19e76af87fe9d5c18815f20c9e31057ea5179f0b173dd4594ac30c200e69
|
| 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 Aug 13, 2026.
Transparency logRelease files / binderqc-0.3.0-py3-none-any.whl
| Download URL | binderqc-0.3.0-py3-none-any.whl |
|---|---|
| Size | 23.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4da631d6f56cf08ef4b6594d381fffc14dd6380fad324fe2a7c87a59b0eb953c
|
|
BLAKE2b-256 checksum How to use checksums |
655012b65a94d8b8f61adc9187ca9ee1cc810f088f6540622927435f2c871e14
|
| 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 Aug 13, 2026.
Transparency log