# 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:** 100

<div class="post-metadata">

**Author:** ![Mikhail\_Kagalenko](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mikhail_kagalenko/32/13257_2.png) [@Mikhail\_Kagalenko](https://discourse.julialang.org/u/Mikhail_Kagalenko)\
**Post date:** [March 18, 2026, 10:44am UTC](https://discourse.julialang.org/t/policies-around-registering-ai-created-packages-in-general/136228/100 "2026-03-18T10:44:57Z")

</div>

> [@Tortar](#):
>
> Actually to me it seems too strict for many projects, i.e. I used LLMs to find bugs in [Ark.jl](https://juliaregistries.github.io/General/packages/redirect_to_repo/Ark)

I think that “finding bugs” use case is the single one use of LLM that shouldn’t be  
subject to any additional rules, so long as the fixes for those bugs are produced  
by humans.

> [@Tortar](#):
>
> In general, my main concerns about AI is the current level of control by big entities

I agree that this is a major issue, if a code base becomes increasingly slopified,  
that creates a vulnerability in the project – human developers may become  
increasingly unwiling or even unable to contribute, so the whole project  
tutns out to be fully controlled by a corporation.

---

_[View the full topic](https://discourse.julialang.org/t/policies-around-registering-ai-created-packages-in-general/136228)._