Licensing
Under which licence MeteorGPL redistributes the code, what is removed from the archives and why, why licence checks are never altered, and what the licence profiles mean.
Version 2026-10-07.2 · Last updated
On this page
The code is redistributed under the GPL each package declares
WordPress plugins and themes derive from WordPress, which is licensed under the GNU General Public License, and the vast majority of vendors declare their products under the GPL (version 2 or later, or version 3). The GPL grants anyone who receives the code the right to copy, modify and redistribute it. WebbingApps OÜ, which operates MeteorGPL, exercises that right: each package is redistributed under the licence declared in the product's own headers, and that declaration (as an SPDX identifier) is shown on the package page and in the API. Products that declare a licence that is not the GPL are not imported.
What is removed and why
A vendor's GPL declaration covers the code. Images, fonts, audio, video, documents and demo content bundled with a product are frequently licensed separately (stock photos, commercial fonts, “split licence” products on marketplaces), so the repository does not redistribute them:
- raster images are replaced by placeholders of the same dimensions, so layouts keep working; SVG files are kept as code;
- font files are removed, except icon fonts the plugin or theme needs to render its own interface;
- audio, video, documents (PDF, Office files), demo and sample content and nested archives are removed;
- PHP, JavaScript, CSS, translations, text and HTML files are always kept.
The removed files are available from the vendor with your licence. Every version lists what was removed in its build report; the package page shows the resulting licence profile.
Licence profiles
- gpl-full — The product declares the GPL for everything it ships; assets are still removed by the policy above, by default.
- split-envato — A marketplace “split licence”: code under the GPL, assets under a separate licence. Assets are removed.
- undeclared — No licence header was found; the product is treated as GPL on the basis of its derivation from WordPress, with the same removal of assets. A takedown request from the rights holder is honoured as described in the takedown policy.
- non-gpl-declared — The product declares a licence that is not the GPL. It is not imported and never appears here.
Licence checks are never altered
The vendor's licence, activation and update code is shipped exactly as written. Nothing is patched, stubbed or removed to make a product run without a key, and archives that arrive with such modifications are either restored to the original code or not published. This keeps the vendor's business model intact and keeps you entitled to the vendor's updates and support.
Keys are bought from the vendor
To activate a plugin or theme, enter the key you bought from the vendor in WordPress, as you would with a download from the vendor's portal. The repository provides the code in a form that Composer can install, version and reproduce; it does not provide keys, and the subscription is not a product licence. Each package page links to where the vendor sells licences.
Questions
Vendors and customers can write to WebbingApps OÜ at [email protected].