Licences and the license key vault
What the subscription covers, why you still need the vendor's license key, and how to keep your keys with expiry reminders.
Packages are redistributed under the GPL their vendors declared. The vendors' license checks are intact: to activate a plugin or theme in WordPress, use a license key you bought from the vendor. Support and updates inside WordPress come with that key, not with this repository.
Artwork, fonts and media that may be licensed separately are replaced or removed; the licensing page explains why.
The license key vault
Settings → License keys keeps the keys you bought, encrypted. Each key shows on its package's page, and we remind you 30 and 7 days before it expires.
Before you start
Opening the vault asks for your password once every few hours (or a confirmation with GitHub or Google if your account has no password).
Add a key
- Open Add a license key.
- Give it a Name (1), for example Elementor Pro — agency.
- Under Package (optional) (2) enter the Composer name (
meteorgpl-plugin/elementor-pro) to show the key on that package's page. - Paste the License key (3). Vendor, the e-mail address you bought it with, the number of sites and the purchase date are optional.
- Enter Expires on (4) to get the reminders.
- Select Save to vault (5).
The quickest way: on a package page, use Add it to your vault in the Your license box; the form opens with the package filled in.
Use and edit a key
Open a key in the list to see it in full.
- The label (1) says when it expires; it turns yellow 30 days before and red once expired.
- Copy (2) puts the key on your clipboard, ready to paste into WordPress.
- Change the details and select Save (3), or Remove the key.
Questions
Who can see my keys? Only you. They are stored encrypted and shown only to your account.
Do I need a key to install with Composer? No. Composer installs the package with your Composer token; the vendor's key is for activating it in WordPress.
Did this not answer your question? Contact support.



