# Policies around registering AI-created packages in General? **URL:** https://discourse.julialang.org/t/policies-around-registering-ai-created-packages-in-general/136228 **Category:** Tooling **Tags:** package, registry, ai **Created:** [March 16, 2026, 4:25pm UTC](https://discourse.julialang.org/t/policies-around-registering-ai-created-packages-in-general/136228 "2026-03-16T16:25:33Z") **Posts on this page:** 1 **Showing post:** 175

### Author: ![goerz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/goerz/32/3269_2.png) [@goerz](https://discourse.julialang.org/u/goerz) #### Post date: [March 19, 2026, 2:37pm UTC](https://discourse.julialang.org/t/policies-around-registering-ai-created-packages-in-general/136228/175 "2026-03-19T14:37:35Z")

Yes! As I’ve said _repeatedly_: > [@Policies around registering AI-created packages in General?](https://discourse.julialang.org/t/policies-around-registering-ai-created-packages-in-general/136228/110): > > I need to remind everyone again that our existing policy makes a huge distinction between AI-assisted coding where a human guides the use of the AI and vibe-coding, where the human has no idea what is going on. The former is encouraged, the latter forbidden for registered packages. Using AI to find and fix bugs is more than welcome. The SciML organization is doing that extensively, and it that is being cited as an appropriate use of AI in the guidelines. The terms “vibe-coding” and “slop” are _defined_ in our guidelines! > [@Policies around registering AI-created packages in General?](https://discourse.julialang.org/t/policies-around-registering-ai-created-packages-in-general/136228/49): > > @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: The guidance on General links to a prior discussion here: > [@Ronis\_BR](#): > > I think we are having a misunderstanding here. Probably, I am not being able to express my opinion clearly. No, you are not responding to what was actually said, or what the actual policies are. You’re responding to a perceived “absolute position” that does not exists, with an apparent definition of “vibe-coding” that in no way matches the definition of vibe-coding that exists in the guidelines. Can you look at what the actual guidelines are and what has been said about their intent in this and [the previous thread](https://discourse.julialang.org/t/should-general-have-a-guideline-or-rule-preventing-registration-of-vibe-coded-packages/133205), and stop arguing against strawmen? > [@Ronis\_BR](#): > > Notice that all this discussion started because the contributions of @kahliburke were said to be “borderline with respect to” the guidelines. No, that is _not_ what was said! What got a raised eyebrow was a comment > [@\[ANN\] Tachikoma.jl — A terminal UI framework for Julia](https://discourse.julialang.org/t/ann-tachikoma-jl-a-terminal-ui-framework-for-julia/135878/77): > > Just for the record, I’m totally fine if you were to submit a PR that was 100% generated using LLM based coding assistants. I will have my agent review what your agent generated, and it’ll get done very quickly! That is, merging PRs that were generated by LLMs without any human supervision. That is at least on the road (“borderline”) to vibe-coding, something that will lead to poor software quality if done at a large scale. It does not mean that the actual full Tachikoma package or @kahliburke’s development practices in their entirety are “borderline”. > [@Policies around registering AI-created packages in General?](https://discourse.julialang.org/t/policies-around-registering-ai-created-packages-in-general/136228/60): > > Just to be extra clear, again: I’m not seeing any issues with the [Tachikoma.jl](https://juliaregistries.github.io/General/packages/redirect_to_repo/Tachikoma) package from which this discussion spun off. You definitely seem to have sufficient experience to use the agent-workflow effectively. So: more power to you! There’s absolutely no issue with LLM-assisted coding. It’s great when it can make people more productive, and I also agree that when used correctly, it has great potential to improve the quality of packages. For Tachikoma in particular, that seems to be the case… I would note that the package was registered (which included my review, without being flagged), long before this entire discussion. The way the no-vibe-coding guideline gets applied in practice is that when I or anyone else reviewing registrations notices obvious and egregious slop, we can raise a flag and link to that policy without having to explain over and over again what exactly we expect for registered packages. It is not a blanket policy against LLM usage. > [@Ronis\_BR](#): > > > [@mbauman](#): > > > > Be human and respect the humanity of others (that is, don’t inundate others with drivel you’ve not even cared to look over yourself) and you’re in good shape. > > Yes, that’s what I am trying to defend all along. Great, because that’s what the guidelines actually are. So we’re all in agreement, and maybe we can stop arguing in circles? --- _[View the full topic](https://discourse.julialang.org/t/policies-around-registering-ai-created-packages-in-general/136228)._