Indeed, and that's through the API. If you use Claude Chat/Code and even if you then turn off web search, it still has access to some of its tools (for doing calculations, running small code snippets etc.) and that environment contains chardets code 4 times:
It's not surprising that they were able to create a new, working version of chardet this quickly. It seems the author just told Claude Code to "do a clean room implementation" and to make sure the code looks different from the original chardet (named several times in the prompt) without considering the training set and the tendency for LLMs to "cheat".
It also shows why this approach is questionable. Opus 4.6 without tool use or web access can provide chardets source code in full from memory/training data (ironically, including the licensing header): https://gist.github.com/yannleretaille/1ce99e1872e5f3b7b133e...
We are Wingback, a new startup building the infrastructure needed to make it easier for anyone in the future to build and grow a SaaS product. If you worked for a SaaS startup before, the chances are high that you got asked to build a custom pricing plan with a custom feature set for one specific client at some point. If so, you probably hated the task and no one in your team wanted to work on it either. Wingback makes it possible that developers won’t ever have to do that again.
We have a great core team on 5 continents, are currently part of YC and are looking for a few more experienced engineers to join us. My co-founder and I have already built and exited a startup from zero to a team of dozens of engineers and $1m+ in revenue in the in the past, so things have been running (mostly) orderly since the beginning. We are currently onboarding the first customers and I'm looking forward to start adding more advanced features!
We are currently looking for:
* Senior Rust Backend Engineer
* Integration Engineer (mixed stack with focus on typescript and some rust)
Our previous company was one of the earliest supporters of rust[0] and we are committed to continue to support the amazing rust community through sponsorships and open source contributions.
We do not care about your academic degrees or where you are from, but about the stuff you did and what you could create in the future given the right opportunities. If you are interested in working with us, write me an email at work_with_yann_hn₍ₐₜ₎wingback.com and tell us about the projects you worked on that you are the most proud of and which technological feats of the past inspire you.
It's not surprising that they were able to create a new, working version of chardet this quickly. It seems the author just told Claude Code to "do a clean room implementation" and to make sure the code looks different from the original chardet (named several times in the prompt) without considering the training set and the tendency for LLMs to "cheat".