In the last 90 days they had 11 contributors that changed c,cpp, and c header files with at least 10 lines of code churn: https://public-001.gitsense.com/insig

In the last 90 days they had 11 contributors that changed c,cpp, and c header files with at least 10 lines of code churn: https://public-001.gitsense.com/insights/github/repos?p=commits&q=file-churn%3A%3E%3D10%2Blangs%3Ac_header%2Ccpp%2Cc%2Bwindow%3A90&r=github%3Acookiengineer%2Faudacity&v=repo https://public-001.gitsense.com/insights/github/repos?p=comm... The user crsib appears to be the main contributor to audacity, so I would have to imagine others would have to pick up the slack for a fork to be viable. cookiengineer also changed 71 files https://public-001.gitsense.com/insights/github/repos?p=commits&q=authors%3Acookiengineer%40protonmail.com%2Binvolves%3Acookiengineer&r=github%3Acookiengineer%2Faudacity&v=repo https://public-001.gitsense.com/insights/github/repos?p=comm... so he/she will have to constantly monitor these files moving forward, for the fork to be stable/similar to audacity/audacity, which I am not sure if he/she/others are interested in doing this for the long term, but I guess time will tell. Full disclosure: I'm the creator of the tool that I linked to