@Mikhail_Kagalenko , I’d encourage you to pay particularly close attention to @Goerz ’ comments as he is a core maintainer of the General registry. In particular, see that there is a policy about vibe-coding :
goerz:
We have a policy against vibe-coded packages , but it’s neither realistic, useful, or enforceable to ask that “no LLM has ever touched any part of this code”. I would expect there not to be any actively developed packages in the near future that would qualify for this. People are of course encouraged to disclose in some form of their choosing when they use LLMs as a very significant part of their workflow. But at the end of the day, our expectation is that humans have ownership their code. You can use an LLM, or any other automated tools such as linters and formatters, to write code or tests or documentation on your behalf, but you’re responsible for whatever you commit.
The guidance on General links to a prior discussion here:
Note: here vibe-coding means “building software with an LLM without reviewing the code it writes”.
7 Likes