Skip to main content

COFOLDER

COFOLDER is a collection of command-line workflows for protein-ligand co-folding and pre-cofolding diagnostics.

The supported public entry points are:

  • bias: inspect protein and ligand reference overlap directly from system.yaml
  • validate: run a single runner-backed co-folding workflow
  • screen: run validate-style workflows across a ligand library
  • oracle: return one scalar metric from a runner-backed run

COFOLDER has a backend-free base install for configuration, input handling, resource access, and analysis-independent library paths. Install the analysis extra for clustering, affinity statistics, interaction processing, and plotting; prediction workflows additionally use one backend extra. Structural-confidence outputs, validation metrics, and affinity-related outputs are treated as distinct concepts; structural confidence should not be described as a proxy for binding affinity.

Start Here

If you are new to the repository, use this path:

  1. Install COFOLDER with the backend you need. See docs/getting-started/installation.md.
  2. Run your first command. See docs/getting-started/quickstart.md.
  3. Pick the workflow that matches your task. See docs/user-guide/overview.md.
  4. Move to worked examples and hands-on tutorials. Use examples/README.md, docs/tutorials/index.md, and tutorials/README.md.

Installation

COFOLDER requires Python 3.11 or 3.12.

Base install:

git clone https://github.com/CDDLeiden/COFOLDER.git
cd COFOLDER
python -m pip install -e .

Recommended analysis and prediction install with the default backend:

python -m pip install -e ".[analysis,boltz2]"

OpenFold3 install:

python -m pip install -e ".[analysis,openfold3]"
cofolder-tools setup-openfold3

The bias workflow does not require a co-folding backend. Install .[analysis] for its complete plotting artifact set and other optional analysis features.

Installed setup and data-preparation helpers are grouped under cofolder-tools. Run cofolder-tools --help to copy the bundled examples, prepare OpenFold3, install MMseqs2, or fetch/build bias-training data.

Common Commands

cofolder [-h] [-v] {bias,validate,screen,oracle}

Examples:

cofolder bias \
  --system_path system.yaml \
  --wrk_dir ./bias_out \
  --custom_protein_reference_path custom_protein.csv \
  --custom_ligand_reference_path custom_ligand.csv

cofolder validate \
  -s examples/system.yaml \
  -o examples/options.yaml \
  -w ./validate_out

cofolder screen \
  -s examples/system_screen.yaml \
  -o examples/options.yaml \
  -c examples/ligand_screen.csv \
  --col_id compound_id \
  --ligand_chain B --smiles_column smiles \
  -w ./screen_out

cofolder oracle \
  -s examples/system.yaml \
  -o examples/options.yaml \
  --input_smiles "CCO" \
  --output_metric system__confidence_score \
  --scoring_functions confidence_metrics \
  --aggregate first

For detailed setup, workflow selection, and command options, use:

For CLI-independent execution and backend integration, use the Python API flow references:

Repository Guide

These top-level paths now have distinct roles:

  • docs/: authoritative public documentation for installation, workflow selection, tutorials, and API reference
  • examples/: copyable input files and small fixtures used by quickstarts and docs
  • tutorials/: interactive notebook tutorials for hands-on exploration
  • scripts/: helper utilities for optional setup and bias-data preparation
  • LICENSE and THIRD_PARTY_SOFTWARE.md: repository licensing and third-party attribution

For a short tour of how these pieces fit together, see docs/getting-started/repository-tour.md.

Folder-Specific Notes

Documentation

The MkDocs site is the best public-facing documentation surface. To build it locally:

python -m pip install -e ".[docs]"
mkdocs serve

The docs site complements, rather than replaces, the repository tutorials:

  • docs/ is the curated reading path
  • examples/ is the copy-and-run path
  • tutorials/ is the interactive notebook path

Licenses

COFOLDER is released under the MIT License. Third-party attributions for adapted or bundled components are listed in THIRD_PARTY_SOFTWARE.md.

Citation metadata for COFOLDER 1.0.0 is provided in CITATION.cff. The publication and archival identifier will be added after those records are final.

Metadata

Release files for cofolder 1.0.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 cofolder 1.0.0
File Size Uploaded Provenance Actions
cofolder-1.0.0.tar.gz 776.5 kB With provenance Details for cofolder-1.0.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for cofolder 1.0.0
File Interpreter ABI Platform Actions
cofolder-1.0.0-py3-none-any.whl Python 3 none any Details for cofolder-1.0.0-py3-none-any.whl

Total release size: 1.2 MB

Release files / cofolder-1.0.0.tar.gz

Download URL cofolder-1.0.0.tar.gz
Size 776.5 kB
Tags Source
SHA-256 checksum
How to use checksums
e84a061ae8ea9dd0dbb9fea5d37c9157452d47b30a48f0780102b085fecb44d3
BLAKE2b-256 checksum
How to use checksums
634f8d6d3cf76fbb6fb4eb4261c5fb7ee67ef6cc957b1ef33e81e73fc7633761
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 6, 2026.

Transparency log

Release files / cofolder-1.0.0-py3-none-any.whl

Download URL cofolder-1.0.0-py3-none-any.whl
Size 453.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
347bc5dcbdc4e9b6d99f5e1bde742c532029052b67eedbac42066cf4fe8644d2
BLAKE2b-256 checksum
How to use checksums
8d5595b8d73bbf3a40fbd9fbdc7cdbddb00d31c19b3144d4c1b34733fa268206
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 6, 2026.

Transparency log

Security for cofolder 1.0.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.

Select from 2 files

Attestation for cofolder-1.0.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 6, 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

This release

1.0.0 This release

2 release files Full provenance

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