Posted by Deni Mintsaev on 20 Nov 2026
I'm sad to announce that RecordRanks will no longer be an open source project moving forward. I originally started this as a fully open source and community-oriented project in July 2023, and it has remained both of those things ever since. While I'm still 100% committed to the community aspect of it, I no longer feel comfortable having the code base be publicly accessible in light of all of the software security vulnerabilities that are now being discovered by AI, and the accessibility of AI capable of performing cyber attacks. I expand on this a little more at the end of this post.
I fully understand the potential for this being perceived by some as motivated by some sort of business interest on my part, since RecordRanks also became a commercial project earlier this year, which is the main reason I've been putting off making this decision. The truth is, I have always valued open source software, and always wanted my projects to be open source, even with business interests involved. But considering that we now have over 2700 user accounts registered across Cubing Contests and the RecordRanks Platform, and the fact that I'm still only working on this as a side project, I believe the risks now outweigh the benefits of open source.
I'll link the final publicly accessible version of RecordRanks later today. I'll also share access to the main RecordRanks repository that I'm now maintaining privately with the Cubing Contests admin team. My main aim here is to ensure RecordRanks doesn't become an abandoned project if I were to one day become unable to continue maintaining it for whatever reason. However, I currently have no intentions of abandoning RecordRanks, and in fact I'm really looking forward to adding more features, particularly the Tournament Brackets feature, which is now 28% community-funded on Ko-fi!
As for my reasons behind this decision, this is down to the fact that there are now AI models out there that can perform cyberattacks at scale, sometimes even finding zero-day vulnerabilities to infiltrate systems. While I take security of our server seriously, I'm only one developer working on this in my free time, and it's not realistic for me to be able to keep up with AI agents if someone instructed their AI to attack our servers. While I could take the idealistic approach and stick with my open source principles, at the end of the day, I'd be putting our users' data at risk. It's possible that in the future the tech industry finds reliable ways of dealing with these sorts of attacks, in which case I'd be more than willing to integrate some of those defences and make RecordRanks open source once again.
I hope for your understanding, and thank you for reading this far!