MiTo (Mitochondrial single-cell lineage tracing Toolkit)
Mitochondrial single-cell multi-omics in Python.
MiTo infer clonal ancestries in single-cell data from natural mtDNA variation.
The framework provides the infrastructure to convert MAESTER, scmtATAC-seq and RedeeM pre-processing outputs into Allele Frequency Matrices (i.e., AnnData objects), filter informative mtDNA variants, genotype individual cells, and infer mitochondrial phylogenies and clones for dowstream multi-omic analysis.
Installation
pip install scmito
Requires Python 3.11+.
import mito as mt
print(mt.__version__)
Quick start
import scanpy as sc
import mito as mt
# Allele Frequency Matrix (cell x site AnnData with AD / DP layers)
afm = sc.read('afm_unfiltered.h5ad')
# Cell and variant filters, distances in mtDNA mutation space
afm = mt.pp.filter_cells(afm, cell_filter='filter2')
afm = mt.pp.filter_afm(afm, filtering='MiTo')
# Phylogeny and clonal inference
tree = mt.tl.build_tree(afm, precomputed=True, solver='UPMGA')
annotator = mt.tl.MiToTreeAnnotator(tree)
annotator.clonal_inference()
# Visualization
mt.pl.plot_tree(tree, features=['MiTo clone'])
See getting-started tutorial for the full vignette.
API
MiTo follows the scverse layout, composing with scanpy and anndata:
| Module | Purpose |
|---|---|
io |
Build AFMs from pre-processing outputs, read/write Newick tree objects |
pp |
Cell and variant filtering, genotying, distances, kNN graphs, embeddings |
tl |
Tree building, clonal inference, clustering, fate bias |
pl |
Trees, heatmaps, embeddings, coverage and variant-spectrum plots |
ut |
Metrics, helpers |
Supported platforms: scRNA-seq (MAESTER), scmtATAC-seq and 10x MultiOme (RedeeM).
Full reference: MiTo docs.
Development
git clone https://github.com/andrecossa5/MiTo.git
cd MiTo
pip install -e ".[test]"
pytest
Citation
If MiTo is useful in your work, please cite:
Cossa, A. Dalmasso A. et al. MiTo: mitochondrial lineage tracing and single-cell multi-omics. Nat Comm (2026). https://doi.org/10.1038/s41467-026-71607-5
MiTo builds on the Cassiopeia package for phylogeny reconstruction and data infrastructure. Please, cite it as well.
Releases
See CHANGELOG.md.
License
MIT — see LICENSE.
Metadata
Release files for scmito 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| scmito-0.2.1.tar.gz | 1.6 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scmito-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.2 MB
Release files / scmito-0.2.1.tar.gz
| Download URL | scmito-0.2.1.tar.gz |
|---|---|
| Size | 1.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
30891cf1f307a489904606bbf7b31bce22c1c7d68e22e7c50f49074a25ee6dd1
|
|
BLAKE2b-256 checksum How to use checksums |
7996a31eeb2c2a9567956a5a5a30a26a31cd23db2ef50100f21a5438c53fa6d5
|
| 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 15, 2026.
Transparency logRelease files / scmito-0.2.1-py3-none-any.whl
| Download URL | scmito-0.2.1-py3-none-any.whl |
|---|---|
| Size | 1.6 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
08cfa2d3a17a71c83fea8fc69030cee7b13c743e90c4f6eda46b7790afa50c64
|
|
BLAKE2b-256 checksum How to use checksums |
0ae30865118ddfb6c4d517cce908b5edf841a5f9651753ed370603afb92f0bac
|
| 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 15, 2026.
Transparency log