Introduction
On this page you can see the beating heart of sanger-tol - the size of our community and the output of our work.
Please bear in mind the following points when looking over these numbers:
- Pipelines maybe worked on before they are transferred to sanger-tol. The age, stars and other metrics of the original parent repository are not shown.
- Metrics are for the default (
main) branch only - Commits and contributors are only counted if associated with a GitHub account
nextflow pullandnextflow runuses git to clone a remote repo the first time it runs, so the clones count gives some idea of usage. However:- Unique cloners is based on IP address, so will under-represent institutional users sharing a single external IP address
- Unique cloners is based on IP address, so will over-represent cloud users using multiple IP addresses
- Traditional HPC centres may share workflow installations, so only have one clone for many users / pipeline runs
- Cloud users will typically spin up a new instance and clone the workflow every time that they run a pipeline.
- Clone counts and repositoriy views are only available for two weeks - longer term data collection for sanger-tol repos started in July 2023 This is when we started counting the totals.
- Metrics are fetched once per day (last checked 2025-10-06).
Community
The numbers below track our growth over the various channels that the sanger-tol community operates in.
Click a number to see how the community has grown over time
GitHub organisation members
We use GitHub to manage all of the code written for sanger-tol. It's a fantastic platform and provides a huge number of tools. We have a GitHub organisation called sanger-tol.
It is not required to be a member of the sanger-tol GitHub organisation to contribute. However, members get the sanger-tol logo listed on their profile page and full write-access to all sanger-tol repositories.
By default, organisation membership is private. This is why you'll see a lower number if you visit the sanger-tol organisation page and are not a member.
GitHub contributors
Anybody can fork sanger-tol repositories and open a pull-request. Here we count how many different people have contributed at least one commit to an sanger-tol repository, or created or commented on an issue or pull-request.
Plot truncated to start of 2022 (some pipelines moved to sanger-tol so have older contributions).
Code stats
Whilst we always prefer quality over quantity, these numbers reflect the work output from the sanger-tol community.
Repository traffic
Every time a nextflow user pulls a sanger-tol pipeline, the repository is cloned. Here we can track how much that happens across all sanger-tol repositories. Please note that these numbers come with some caveats [ see more ].
Additionally, GitHub tracks how many times people view repository web pages on github.com.
Pull Requests
When people contribute code to a sanger-tol repository, we conduct a "Pull request" - other members of the sanger-tol community review the proposed code and make suggestions, before merging into the main repository.
Pull Request response times
Pull-requests are reviewed by the sanger-tol community - they can contain discussion on the code and can be merged and closed. We aim to be prompt with reviews and merging. Note that some PRs can be a simple type and so very fast to merge, others can be major pipeline updates.
First response is when a comment is made by a GitHub user other than the original PR author
Issues
GitHub issues can be created to log feature requests, bug reports or questions.
Issue response times
A sign of an active community is a quick response time to issues. Here we see a frequency histogram of how long it takes to respond to and close issues.
First response is when a comment is made by a GitHub user other than the original issue author
Contributor Leaderboard
We value each and every contribution to sanger-tol, no matter how small. However, that doesn't mean that we can not get competitive!
Here are the latest stats of who has contributed the greatest number of commits.
Remember
- There is more to contributing than commits! We're not counting issue comments, reviews or anything else here.
- People merging pull-requests get bonus commit counts from those merge commits.
- Some people commit often, others not so much. So it's not a perfect representation of amount of work - just a bit of fun!
mainbranch only, and all of the other caveats..
@DLBPointon
@muffato
@yumisims
@weaglesBio
@priyanka-surana
@prototaxites
@gq1
@tkchafin
@BethYates
@alxndrdiaz
@SandraBabirye
@zb32
@yz533cb
@mahesh-panchal
@ksenia-krasheninnikova
@eeaunin
@cduong11
@juliaapolonio
@sanger-tolsoft
@sainsachiko
@nf-core-bot
@sujaikumar
@scorreardPipeline numbers
All sanger-tol pipelines are only considered stable when they have at least one release. Until then, they are classed as "in development".
Pipelines
Click a row to see detailed statistics for that repository.
| Name | Age | Releases | Committers | Commits | Stargazers | Watchers | Network Forks | Clones | Unique cloners | Repo views | Unique repo visitors | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Total: | 17 pipelines | 96 | 23 unique | 7905 | 138 | 96 | 54 | 40233 | 8760 | 125539 | 15729 | |
| sanger-tol/blobtoolkit | 3 years | 9 | 11 | 888 | 13 | 6 | 6 | 3293 | 713 | 11950 | 1753 | |
| sanger-tol/ensemblgenedownload | 3 years | 5 | 3 | 145 | 1 | 5 | 2 | 613 | 247 | 670 | 153 | |
| sanger-tol/ensemblrepeatdownload | 3 years | 3 | 3 | 153 | 1 | 5 | 1 | 546 | 216 | 577 | 124 | |
| sanger-tol/genomeassembly | 3 years | 0 | 9 | 344 | 23 | 12 | 4 | 3582 | 713 | 15003 | 1880 | |
| sanger-tol/genomenote | 3 years | 14 | 7 | 732 | 26 | 5 | 7 | 4274 | 914 | 13414 | 1897 | |
| sanger-tol/insdcdownload | 3 years | 5 | 4 | 217 | 1 | 6 | 3 | 984 | 363 | 1774 | 266 | |
| sanger-tol/readmapping | 4 years | 10 | 5 | 404 | 13 | 4 | 6 | 2567 | 670 | 12605 | 1503 | |
| sanger-tol/sequencecomposition | 3 years | 2 | 3 | 144 | 2 | 5 | 3 | 748 | 264 | 1069 | 234 | |
| sanger-tol/treeval | 3 years | 9 | 7 | 2654 | 28 | 7 | 5 | 7353 | 1224 | 32448 | 3416 | |
| sanger-tol/variantcalling | 3 years | 12 | 9 | 383 | 9 | 8 | 9 | 2352 | 646 | 11418 | 1176 | |
| sanger-tol/curationpretext | 2 years | 11 | 7 | 444 | 13 | 7 | 5 | 3543 | 947 | 7222 | 1221 | |
| sanger-tol/ascc | 2 years | 6 | 5 | 987 | 5 | 7 | 1 | 5386 | 969 | 11814 | 1253 | |
| sanger-tol/genealignment | 1 year | 0 | 1 | 6 | 0 | 4 | 0 | 124 | 105 | 156 | 47 | |
| sanger-tol/ear | 1 year | 3 | 1 | 64 | 0 | 4 | 1 | 781 | 211 | 1189 | 149 | |
| sanger-tol/metagenomeassembly | 2 years | 7 | 3 | 225 | 3 | 5 | 0 | 3212 | 341 | 2048 | 464 | |
| sanger-tol/zippypretext | 6 months | 0 | 2 | 48 | 0 | 4 | 0 | 257 | 81 | 507 | 53 | |
| sanger-tol/variantcomposition | 9 months | 0 | 2 | 67 | 0 | 2 | 1 | 618 | 136 | 1675 | 140 | |
| Name | Age | Releases | Committers | Commits | Stargazers | Watchers | Network Forks | Clones | Unique cloners | Repo views | Unique repo visitors |