Development, dependency structure, workflow, and turnaround time. (a) contributing authors and (b) added recipes over time. (c) largest connected component of directed acyclic graph of Bioconda packages (nodes) and dependencies (edges). Highlighted is the induced subgraph of the CNVkit \cite{Talevich2016} package and its dependencies spanning Python, C/C++, and R ecosystems (node coloring as defined in Fig. 1a in main text, squared node represents CNVkit). (d) GitHub based development workflow: a contributor provides a pull request that undergoes several build and test steps, followed by a human review. If any of these checks does not succeed, the contributor can update the pull request accordingly. Once all steps have passed, the changes can be merged. (e) Turnaround time from submission to merge of pull requests in Bioconda. (f) Workflow for using Conda packages. After the Bioconda channel has been set up, packages can be searched and installed directly. Alternatively, isolated software environments can be created.