The checklists below were developed for Extension Developers (those who want to be listed in the JED) and JED Editors (to stay consistent with approval processes). To be approved and listed in the JED, an entry must be verified in a 4 step checklist process. Follow the checklists in the order that they appear here to give your entry the best possible chance of being listed in the JED.
Installation and Functionality Checklist
Submissions Checklist
You may submit up to 3 listings at one time. Bulk submissions are not allowed without prior approval from the JED Team. If you are seeking bulk submissions approval, please submit a support ticket after you have submitted 3 listings to be approved.
List A1: General Submission Verification
The following criteria is considered while approving a listing based on the files that were submitted.
| Item | What types of files were submitted? | Is the entry publishable? |
| 1 | Core Joomla hacked files | No. Please contribute code to core Joomla. |
| 2 | Hacked files from other extensions | No. Please send code contributions to the extension developer. |
| 3 | Joomla templates | No. |
| 4 | Joomla languages | No. Please make contributions to the Translations Working Group. |
| 5 | Extension languages | No. Please send the language file to the extension developer. |
| 6 | Extension created by others | No. An extension must be submitted by the author. |
| 7 | Forked extensions | Maybe. See the Forked Extensions requirements. |
List A2: Links Verification
The following criteria is considered while approving a listing based links that were provided in the submission.
| Item | Link | Is the entry publishable? |
| 1 | Main website | Yes, as long as the main website link works. |
| 2 | Download links that point to file share sites or a list of extensions | No. |
| 3 | Shortened URLs | No. Remove shortened URLs and use full URLs. |
| 4 | Documentation, support or demos not working properly |
No.
|
| 5 | Copy of extension not uploaded | No. If the link is publicly available, download and include it in the JED entry. |
List A3: Author Verification
The following criteria is considered while approving a listing based on the developer who submitted the entry.
| Item | What? | Is the entry publishable? |
| 1 | The user submitted an extension created by someone else. |
No, an extension must be submitted by the author. |
| 2 | The developer has been blocked. | No, blocked developers must wait to be reinstated to submit an entry. |
List A4: Name Entry Verification
The following criteria is considered while approving a listing based on the extension.
| Item | What? | Is the entry publishable? |
| 1 | The name conflicts with another extension. | No. |
| 2 | The word "Joomla" appears in the extension's name. | Maybe - see the Trademark Checklist below. |
| 3 | Part of the word "Joomla" appears in the extension's name. | Maybe - see the Trademark Checklist below. |
| 4 | The name does not comply with the Extension Name rules. | No. Review the Extension Name rules. |
Trademark Checklist
The Joomla! name and logos are registered trademarks in the United States and elsewhere held by Open Source Matters. Permission, from OSM, to use these trademarks is usually required and is only granted subject to specific rules.
Learn more about Joomla Trademark:
Use of "Joomla" in Extension Names
- The use of the word "Joomla" in extension names or domains listed in the JED requires a license by OSM.
- Extension names must include the words "for Joomla" ie: "MyExtension for Joomla" is permitted. "Joomla MyExtension" is not permitted.
- Use of Joomla versions is not permitted ie: "MyExtension for Joomla 3.0"
Getting a License from OSM
To obtain a license to use the word "Joomla" in an extension name or domain name, fill out the following forms and submit them to OSM:
- Domain Name Request (Choose the Department: "Domain/Website Requests")
- Extension Name Request (Choose the Department: "Trademark Use Requests")
Use of other Trademarked Names
Using another trademarked name (if you don't own the trademark) must be include the word "for" ie: "MyExtension for Twitter".
List B1: Joomla Trademark Checklist
The following criteria is considered while approving a listing based on the use of the Joomla trademark and logo.
| Item | What? | Is the entry publishable? |
| 1 | The project site domain uses "Joomla" or a derivative of the word "Joomla". | Only if licensed by OSM. The site will need a Joomla trademark disclaimer at the top of the main page. |
| 2 | The project site displays the Joomla logo using official pictures. | Only if licensed by OSM. |
| 3 | The project site displays an altered Joomla logo. | No. |
| 4 | Extensions that use the word "Joomla" or a derivative of the world "Joomla" in the extension name. | Only if licensed by OSM. |
License Checklist
List C1: GPL License Verification
The following criteria is considered while approving a listing based on the use of the GPL license.
| Item | What? | Is the entry publishable? |
| 1 | The project site lists non-GPL Joomla extensions. | No. he JED will not link to sites that promote and distribute non-GPL extensions. |
| 2 | The project site displays other software (not Joomla extensions) that have other licenses. | Yes. |
| 3 | The entry was submitted as a GPL license. | Yes. |
| 4 | The entry was submitted as a GPL compatible license. | Maybe. See the Special License Verification Checklist. |
| 5 | The entry was submitted with "other" as the license. | Maybe. See the Special License Verification Checklist. |
List C2: General Terms & Conditions Checklist
The following are general terms and conditions considered while approving a listing.
List C2.1 - Entries NOT listed in the JED
| Item | What? | Is the entry publishable? |
| 1 | Encryption for some or all files | See C2.3.8 below. |
| 2 | PHP decoder required (ionCube or something else) | No |
| 3 | Limited use per domain/installation | No |
| 4 | Limited code modifications | No |
| 5 | Limited distribution of PHP files | No |
| 6 | Requires a nondisclosure agreement | No |
| 7 | Limited use of non-GPL media files to a domain/installation | No |
| 8 | Extension-specific for an extension not listed in the JED | No |
"The GPL is a free software license, and therefore permits people to use and even redistribute the software without being required to pay anyone a fee for doing so." Read more: Does the GPL allow me to require that anyone who receives the software must pay me a fee and/or notify me?
List C2.2: Entries listed in the JED
| Item | What? | Is the entry publishable? |
| 1 | The extension is distributed for free. | Yes |
| 2 | The extension requires payment to download. | Yes |
| 3 | The extension requires a subscription to download, install, configure and to get access to direct support or documentation. | Yes |
| 4 | Support is limited based on domains/installations? | Yes |
"The right to sell copies is part of the definition of free software". Read more: Does the GPL allow me to sell copies of the program for money?
List C2.3: Entries Contingent on Other Requirements
| Item | What? | Is the entry publishable? |
| 1 | The entry includes non-GPL files. | Yes, but only for stand alone files that aren't coded (JavaScript, Flash, images, CSS, audio files, etc). |
| 2 | The entry includes non-GPL libraries. | Yes, but only if the libraries are available under a GPL compatible license listed by the Free Software Foundation like LGPL. |
| 3 | The entry has a call home function. |
Yes, but only if:
|
| 4 | The entry uses a light GPL version instead of a full non-GPL version. |
Yes, but only if
|
| 5 | The entry is a modified or forked extension. | Yes, but only if the extension is properly forked. Learn more about Forked Extensions. |
| 6 | The entry includes a backlink to the developer. |
Yes, but only if:
|
| 7 | The entry contains hidden backlinks. | No. As of September 2, 2013, hidden backlinks are not permitted. Links in the PHP GPL Headers are okay if they are commented out. |
| 8 | The entry contains encoded files. |
Yes, but only if:
|
| 9 | The entry contains obfuscated code. |
Generally this is not permitted, but will be considered on a case-by-case basis if obfuscation is used on the file required to verify a support license and obfuscated backlinks aren't present. |
| 10 | The entry bridges to a non-GPL product. |
Yes, but only if
|
| 11 | The entry requires payment to remove links. | Yes, but only if users are allowed to remove the links and the extension works if the files containing the links are edited by users. |
| 12 | The entry is extension-specific for an extension listed in the JED. | Yes, but under special requirements. |
| 13 | The entry is for a script or a library. | Yes, but only if the scripts or libraries are available under a GPL compatible license listed by the Free Software Foundation. |
List C2.4: Entries bridging to Cloud Services / SaaS
| Item | What? | Is the entry publishable? |
| 1 | The extension requires an account on a Cloud Service / SaaS | Yes, but only if the extension is distributed as GPL |
| 2 | The extension is distributed for free and requires a free account on the Cloud Service / SaaS | Yes, but can only be listed as 'Free' if the Cloud Service / Saas offers a free tier that always remains free. |
| 3 | The extension is distributed for free and requires a free trial account on the Cloud Service / SaaS | Yes, but must be listed as a paid extension |
| 4 | The extension is distributed for free and requires a paid account on the Cloud Service / SaaS | Yes, but must be listed as a paid extension |
| 5 | The extension account integration limits the GPL license | No, the Cloud Service / SaaS integration must allow all freedoms granted by the GPL license on the distributed extension. |
List C3: GPL Compatible Licenses
The following criteria is considered while approving a listing based on the use of GPL compatible licenses.
| Item | What? | Is the entry publishable? |
| 1 | The entry uses an LGPL license | Yes, but only for libraries, not extensions. |
| 2 | The entry uses an AGPL license | Yes, but only if you modify the source, and provide that modified code for download. |
| 3 | The entry uses a public domain | Yes. |
| 4 | The entry uses Creative Commons, BSD, MIT or any other free software licenses | No. Only licenses that comply with all terms of the GPL will be considered. |
List C4: Non-GPL Licenses
The following criteria is considered while approving a listing based on the use of non-GPL licenses.
| Item | What? | Is the entry publishable? |
| 1 | The entry includes independent scripts for Joomla | Yes, but only for the "Migration & Conversion" category, not for extensions. |
Installation and Functionality Checklist
List D1: Installation
The following criteria is considered while approving a listing based on the listing installation method.
| Item | What? | Is the entry publishable? |
| 1 | The extension can be installed with the Joomla installer | Yes. Some specific extensions are installed by an extensions-specific installer. |
| 2 | The extension needs a hack to install | No. |
| 3 | The extension needs a manual copy file to install | No, but exceptions are made for payment systems. |
| 4 | The extension hacks Joomla files | No. |
| 5 | The extension changes other extension files | Only if the changes are reverted if the extension is uninstalled. Extension hacks are not allowed. |
List D2: Basic Functionality
The following criteria is considered while approving a listing based on the basic functionality of an extension after it is installed.
| Item | What? | Is the entry publishable? |
| 1 | Component configuration works in the administrator menu | Yes |
| 2 | The module can be published/unpublished | Yes |
| 3 | The plugin can be activated/deactivated in the site | Yes. Legacy plugins require a note on Joomla version compatibility |
| 4 | It's possible to add a new item/category/file in the component | Yes |
| 5 | The extension is intended for public sites | No. The latest version cannot be a "test only" version. |
| 6 | The extension doesn't have update servers configured | No. Update Servers are required for extensions uploaded after 10th January 2017. |
List D3: Security
The following criteria is considered while approving a listing based on the security of an extension after it is installed.
| Item | What? | Is the entry publishable? |
| 1 | The extension is listed on the vulnerable extensions list | No. |
| 2 | The extension requires a 777 permission to install or run | No. |
| 3 | Sanitized: statement for Restricted Access at top of the PHP files. | Yes |
List D4: Uninstall
The following criteria is considered while approving a listing based on the way the extension is uninstalled from Joomla.
| Item | What | Is the entry publishable? |
| 1 | After the uninstall, the site or the administration area returns errors | No. |