Track maintainers
Each track (ports, runtime, agents, docs) has a named maintainer who reviews PRs and signs off releases.
OmicVerse
About
OmicVerse is a Python ecosystem for multi-omics analysis built around three principles:
The core library, omicverse, exposes the unified surface. Around it, the organization maintains pure-Python and pure-Rust re-implementations of widely-cited methods (CopyKAT, hdWGCNA, inferCNV, Monocle, scDblFinder, DoubletFinder, DADA2, mclust, Milo, scHiCluster, BandNorm, NMF…) so users have a parity-audited alternative that doesn't depend on R or rpy2.
An agent layer on top — omicverse-skills and omicclaw — exposes the same methods as callable skills for agent-driven analysis. The project is open-source, community-led, and aligned with the broader scverse ecosystem.
OmicVerse follows a lightweight model: maintainers own tracks, contributions are reviewed in the open, breaking changes go through an RFC.
Each track (ports, runtime, agents, docs) has a named maintainer who reviews PRs and signs off releases.
All design discussion happens in GitHub Issues and Discussions. Contributing doesn't require maintainer status.
Anything that changes a public API, AnnData contract, or benchmark methodology requires a public RFC.
The project follows the Contributor Covenant. Reports go to the maintainer contact in the org README.
Stable releases monthly, patch releases as needed. Each release ships changelog, parity diffs, updated benchmarks.
OmicVerse is independent. Acknowledgments to research groups and funding sources live next to the code they support.
If you use OmicVerse in published work, please cite the framework paper. For specific method ports, also cite the original method.
@article{omicverse, title = "OmicVerse: a unified multi-omics analysis framework", author = "Zeng, Zehua and others", journal = "Nature Communications", year = "2024", url = "https://github.com/omicverse/omicverse" }
Replace this entry with the canonical citation from the project README before publishing.