# The present and the future of package registration

**URL:** https://discourse.julialang.org/t/the-present-and-the-future-of-package-registration/99890
**Category:** Package Management
**Created:** [June 5, 2023, 1:40pm UTC](https://discourse.julialang.org/t/the-present-and-the-future-of-package-registration/99890 "2023-06-05T13:40:11Z")
**Posts on this page:** 1
**Showing post:** 49

<div class="post-metadata">

### Author: ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [June 6, 2023, 5:29pm UTC](https://discourse.julialang.org/t/the-present-and-the-future-of-package-registration/99890/49 "2023-06-06T17:29:43Z")

</div>

> [@Eben60](#):
>
> the registration policy is rather too liberal as it allows (?) to register packages with zero tests and zero documentation

I cannot disagree with this, but note that it is tricky to design automated checks for these that cannot be easily circumvented.

Either we just rely on simple automated checks, and implicitly the decency of package authors, or we need people to review package registrations.

What I find nice is that even with the very liberal registration policy, abuse of the registry is pretty minimal. This is heartening.

---

_[View the full topic](https://discourse.julialang.org/t/the-present-and-the-future-of-package-registration/99890)._