workers-oauth-provider

Cloudflare's Oauth library probably handles some scale. https://github.com/cloudflare/workers-oauth-provider

I would like to see this list too. However, I guess people don't disclose they use AI when making stuff. AFAIK, this https://github.com/cloudflare/workers-oauth-provider repository is made with Claude code.

> So it kinda worked, but I would not use that for anything "mission critical" (whatever this means). It means projects like Cloudflare's new OAuth provider library. https://github.com/cloudflare/workers-oauth-provider > "This library (including the schema documentation) was largely written with the help of Claude, the AI model by Anthropic. Claude's output was thoroughly reviewed by Cloudflare engineers with careful attention paid to security and compliance with standards. Many improvements were made on the initial output, mostly again by prompting Claude (and reviewing the results)."

I get that a lot of folks wouldn't want to keep a log, but it makes me so sad that the wonderful aider 'ai peer' recommends adding aider logs of all sorts to the gitignore on startup. This feels bad for humans, and bad for AI sense-making too. If you are having this dialog, of course you'd want to be able to reflect on that, I'd think. It'd be neat to go further. Keeping the agent instructions alongside engineering docs feels like it makes sense. It'd be neat to see what one could do with Backstage like integration, to build out this existing wonderful corporate knowledge-base. Are there MCP servers yet that can reflect on chat history? Now I want to see a Backstage MCP server even more, one that's extensible by the many Backstage plugins! Shout out to Kenton Varda & cloudflare doing a nice job making a good commit history of AI use on th

To be fair, there was a pretty dumb CVE (which had already been found and fixed by the time the project made the rounds on HN): https://github.com/cloudflare/workers-oauth-provider/securit... You can certainly make the argument that this demonstrates risks of AI. But I kind of feel like the same bug could very easily have been made by a human coder too, and this is why we have code reviews and security reviews. This exact bug was actually on my list of things to check for in review, I even feel like I remember checking for it, and yet, evidently, I did not, which is pretty embarrassing for me.