# Future of the Ansible Community package **URL:** \ **Category:** Project Discussions\ **Tags:** community-wg\ **Created:** [April 11, 2024, 8:54am UTC](https://forum.ansible.com/t/future-of-the-ansible-community-package/4902 "2024-04-11T08:54:55Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [April 11, 2024, 4:37pm UTC](https://forum.ansible.com/t/future-of-the-ansible-community-package/4902/8 "2024-04-11T16:37:29Z")
> [@bcoca](#): > > The community package was created with the expectation that it would eventually fade away as people got used to collections. I can’t say why other people don’t use collections directly, but I think I’ve already mentioned this several times in other places: For “security” (compliance) reasons, our control nodes can’t download collections directly from the internet / galaxy. We need something in between like Sonatype Nexus or similar that works as a caching proxy or so where we can run security and (license) compliance checks centrally. We have a solution that’s accepted by our IT security for PyPI, but not for galaxy. As @felixfontein said [in another context](http://forum.ansible.com/t//4757/29): > [@](#): > > The situation would be a lot better if we’d have more pullthrough caches Different problem, but this would help us to move away from the community package. --- _[View the full topic](https://forum.ansible.com/t/future-of-the-ansible-community-package/4902)._