# ☆List of Cockpit Addons

**URL:** https://discourse.getcockpit.com/t/list-of-cockpit-addons/234
**Category:** Addons
**Created:** [September 1, 2018, 1:20pm UTC](https://discourse.getcockpit.com/t/list-of-cockpit-addons/234 "2018-09-01T13:20:44Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![pauloamgomes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.getcockpit.com/pauloamgomes/32/48_2.png) [@pauloamgomes](https://discourse.getcockpit.com/u/pauloamgomes)
#### Post date: [February 14, 2019, 12:29pm UTC](https://discourse.getcockpit.com/t/list-of-cockpit-addons/234/9 "2019-02-14T12:29:34Z")

</div>

A directory could also work, there are two main aspects:

- Quality - that can be handled maybe by the community with a ranking/rating/etc… of the addon, we can have also a set of rules for that the addon must comply (folder structure, basic php rules, etc…)
- Security - that is a bit more concerning and probably requires validation before an addon is approved, think we need to have you validating that

yep, the CLI command seems a good idea to me, we can maybe think on something similar for what I have in the helpers addon… resuming if and addon provides an info.yaml file with title, description, category that information would be used in the directory/marketplace

Let’s discuss further…

---

_[View the full topic](https://discourse.getcockpit.com/t/list-of-cockpit-addons/234)._