# Plethora of Julia related GitHub organizations and how to know which of them are "official"

**URL:** <https://discourse.julialang.org/t/plethora-of-julia-related-github-organizations-and-how-to-know-which-of-them-are-official/37967>\
**Category:** Community\
**Created:** [April 21, 2020, 2:42pm UTC](https://discourse.julialang.org/t/plethora-of-julia-related-github-organizations-and-how-to-know-which-of-them-are-official/37967 "2020-04-21T14:42:31Z")\
**Posts on this page:** 1\
**Showing post:** 9

<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:** [April 29, 2020, 6:31am UTC](https://discourse.julialang.org/t/plethora-of-julia-related-github-organizations-and-how-to-know-which-of-them-are-official/37967/9 "2020-04-29T06:31:13Z")

</div>

> [@fingolfin](#):
>
> But this is rather fragile.

A somewhat related discussion is

> [@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/plethora-of-julia-related-github-organizations-and-how-to-know-which-of-them-are-official/37967)._