This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 0.0.16a19 instead.
Reason given by maintainers: reason: Ships no trained classifiers; superseded by 0.0.5a2.
Copyright (c) 2019-2025 - President and Fellows of Harvard College. All rights reserved.
SigMA2 - Mutational Signature Analysis in Python
SigMA2 is the Python version of SigMA, a tool developed to detect mutational Signature 3, which is associated with homologous recombination (HR) deficiency. It supports hybrid capture panels, whole-exome, and whole-genome sequencing (WGS) data. While traditional signature analysis tools struggle with data containing few single nucleotide variants (SNVs), SigMA2 is designed to perform well in such settings.
Installation
From PyPI (Recommended)
SigMA2 is currently an alpha pre-release, so --pre is required:
pip install --pre sigma2
Requires Python 3.9-3.12. The upper bound comes from a transitive dependency
(pyranges -> ncls), which publishes no wheels for 3.13 or newer.
One dependency, sorted-nearest, is source-only on every Python version and is
compiled during install, so a working C toolchain is needed (build-essential
on Debian/Ubuntu, base-devel on Arch, Xcode command line tools on macOS).
From Source
git clone https://github.com/sigscape/SigMA2.git
conda env create -f ./SigMA2/environment.yml
conda activate sigmapy310
pip install -e ./SigMA2
Reference data
The package itself ships everything a run needs in the way of models: the data store, the SigMA v1 classifiers, and the panel definitions. Bulk reference data (germline VCFs and repeat regions, ~1.4 GB) is downloaded on demand instead:
sigma2 data list # what exists and what is installed
sigma2 data fetch --all # download everything
sigma2 data verify # re-check checksums
sigma2 info # versions, data directory, disk usage
Files land in a per-user data directory; set $SIGMA2_DATA_DIR to override it,
which is the usual choice on a cluster where one pre-seeded copy is shared.
Reference genomes are separate and larger (~3 GB each): sigma2 data genome hg19.
Access note. Until the accompanying paper is published, the bulk data lives in a private repository.
sigma2 data fetchtherefore needs GitHub credentials with access to it — either rungh auth login, or setSIGMA2_GITHUB_TOKEN. Without access the fetch fails with a 404; the code itself is fully functional, and any data you already hold can be used by pointing$SIGMA2_DATA_DIRat it. Please contact the authors (below) to request access.
Quick Start
Follow these Jupyter Notebooks in numerical order to get started with SigMA2 and its built-in functions!
Documentation & Further Information
Find more here
Contact
Requests for use of the Software for or on behalf of for-profit entities or for any commercial purposes, please contact:
Office of Technology Development Harvard University Smith Campus Center, Suite 727E 1350 Massachusetts Avenue Cambridge, MA 02138 USA Telephone: (617) 495-3067 E-mail: otd@harvard.edu
Citation
If you use SigMA2 in your work, please cite the original SigMA publication as follows:
Detecting the mutational signature of homologous recombination deficiency in clinical samples
<br/>Doga C. Gulhan, Jake June-Koo Lee, Giorgio E. M. Melloni, Isidro Cortés-Ciriano & Peter J. Park<br/>Nature Genetics (2019)<br/>https://doi.org/10.1038/s41588-019-0390-2
Metadata
Release files for sigma2 0.0.5a0
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 |
|---|---|---|---|---|
| sigma2-0.0.5a0.tar.gz | 13.7 MB | With provenance | Details for sigma2-0.0.5a0.tar.gz |
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| sigma2-0.0.5a0-cp39-abi3-win_amd64.whl | CPython 3.9 | abi3 | Windows x86-64 | Details for sigma2-0.0.5a0-cp39-abi3-win_amd64.whl |
| sigma2-0.0.5a0-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.9 | abi3 | Linux glibc 2.17+ x86-64 | Details for sigma2-0.0.5a0-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
| sigma2-0.0.5a0-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | CPython 3.9 | abi3 | Linux glibc 2.17+ ARM64 | Details for sigma2-0.0.5a0-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
| sigma2-0.0.5a0-cp39-abi3-macosx_11_0_arm64.whl | CPython 3.9 | abi3 | macOS 11.0+ ARM64 | Details for sigma2-0.0.5a0-cp39-abi3-macosx_11_0_arm64.whl |
Total release size: 69.2 MB
Release files / sigma2-0.0.5a0.tar.gz
| Download URL | sigma2-0.0.5a0.tar.gz |
|---|---|
| Size | 13.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c2d6b9236ffd952449b505c67ae23648b3ce69ac1f45ace80f9c1d8efab43485
|
|
BLAKE2b-256 checksum How to use checksums |
085a25465b2bde1a8deb358933fb30be99b6162ae84f441b01d7b3199e03541d
|
| 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 7, 2026.
Transparency logRelease files / sigma2-0.0.5a0-cp39-abi3-win_amd64.whl
| Download URL | sigma2-0.0.5a0-cp39-abi3-win_amd64.whl |
|---|---|
| Size | 13.8 MB |
| Tags | CPython 3.9 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
b1856dc5bdbe8aa713cce49e3f88386144cde045784b46608383de771d601542
|
|
BLAKE2b-256 checksum How to use checksums |
37250429ad84ac3322c665ac0ecaa8174e2b43112bac54318933481dff9c54fa
|
| 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 7, 2026.
Transparency logRelease files / sigma2-0.0.5a0-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | sigma2-0.0.5a0-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 13.9 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
c6b5c8530f3e3ff93bbc7c2a5e55c6f66a90fe1e0f326e973b7340cb5945e947
|
|
BLAKE2b-256 checksum How to use checksums |
67909aa576b07369aa4b58383f8bd0ce6868154cc6fbd7ddebdf37eee9326370
|
| 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 7, 2026.
Transparency logRelease files / sigma2-0.0.5a0-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | sigma2-0.0.5a0-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 13.9 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
5cde815eeaed4c3a9241c0f6bb80b35b72a147cc65f8d1fcc4f0f9ea0b69c9b6
|
|
BLAKE2b-256 checksum How to use checksums |
e05c960a940d9065e319d92310fd27d5f2d12d0a88c496260c75d650072f6f93
|
| 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 7, 2026.
Transparency logRelease files / sigma2-0.0.5a0-cp39-abi3-macosx_11_0_arm64.whl
| Download URL | sigma2-0.0.5a0-cp39-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 13.9 MB |
| Tags | CPython 3.9 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
a639849085827069b05de97129a4fc66c696c71c16417c60c66db6fc18254b85
|
|
BLAKE2b-256 checksum How to use checksums |
19ae54b3d4efd817ba3b8e2ec828a68d5e6d19f5b67e361f3439ed46fa5008f4
|
| 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 7, 2026.
Transparency logSecurity for sigma2 0.0.5a0
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 5 files in this release have been uploaded with provenance metadata.
Attestation for sigma2-0.0.5a0.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 Aug 7, 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.