# Published VS unpublished // registered vs unregistered

**URL:** <https://discourse.julialang.org/t/published-vs-unpublished-registered-vs-unregistered/34838>\
**Category:** General Usage\
**Created:** [February 19, 2020, 12:18am UTC](https://discourse.julialang.org/t/published-vs-unpublished-registered-vs-unregistered/34838 "2020-02-19T00:18:34Z")\
**Posts on this page:** 1\
**Showing post:** 5

<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:** [February 19, 2020, 7:11am UTC](https://discourse.julialang.org/t/published-vs-unpublished-registered-vs-unregistered/34838/5 "2020-02-19T07:11:20Z")

</div>

No, registered packages are not checked in detail. You may be interested in

> [@Pkg: attack vectors](https://discourse.julialang.org/t/pkg-attack-vectors/18340):
>
> [Pkg ecosystem: Learning from other's mistakes](https://discourse.julialang.org/t/pkg-ecosystem-learning-from-others-mistakes/18028) has gotten a bit long and wandering, as these discussions tend to. I’d like to have a very focused thread about attack vectors against the security of the package ecosystem. To that end, here are the attack vectors I’ve come up with so far. What are some other attack vectors? Attack: find an existing bug in some package that you can exploit Mitigation: fix the bug yank versions that have it Prevention: testing fuzzing basically anything that …

---

_[View the full topic](https://discourse.julialang.org/t/published-vs-unpublished-registered-vs-unregistered/34838)._