GNU ELPA
elpa.gnu.org
- Free plan
- Open source
- Web
- Self-hosted
What GNU ELPA is
GNU ELPA is the default package repository for GNU Emacs. Users can browse its web archive or open Emacs package listings with `M-x list-packages`, then install packages with `package-install` or from that list. The archive records package versions and descriptions. Accepted packages receive pages that may include descriptions, recent releases, changelog previews, and rendered manuals. GNU ELPA is free, with a listed plan of free, and it has no free trial. Submitted packages must use a GPL-compatible license, ideally GPLv3 or later. Their core functionality must work on systems using only free software, subject to case-by-case exceptions. Significant past and present contributors must sign the FSF copyright assignment. Submissions are emailed to emacs-devel with a description, public Git repository link, and preferred archive. A build server synchronizes repositories and releases a new version when a package Version header changes. The site directs bug reports to `M-x report-emacs-bug` and help requests to the help-gnu-emacs mailing list.
Who it suits
GNU ELPA suits GNU Emacs users who need to browse and install packages. It also suits contributors able to meet its licensing, copyright-assignment, and submission requirements.
Good to know, and what to watch
- Default repository for GNU Emacs packages
- Browse versions and descriptions
- Install through Emacs commands
- Accepted packages can include manuals
- Free plan at no cost
- Web platform only
- No free trial
- Contributor copyright assignment required
- GPL-compatible licensing policy applies
Plans
Every plan and priceGNU ELPA
The verdict
GNU ELPA provides a structured package archive tied closely to GNU Emacs. Its policies and contributor requirements matter when selecting or submitting packages.
What the maker publishes
- Archive format
- An archive is a web-accessible directory containing single-file Lisp packages or tar files with multiple files. source
- Build and releases
- The build server regularly synchronizes package repositories and releases a new version when a commit changes the package’s Version header. source
- Build extensibility
- Package specifications support custom documentation files, NEWS files, build targets, shell commands, version maps and branch selection. source
- Completion integrations
- The cape package provides completion-at-point backends and adapters for Company, Corfu and Emacs's default completion UI. source
- Contribution channel
- Prospective contributors are asked to email emacs-devel with a package description, public repository link and preferred GNU or NonGNU archive. source
- Contributor requirement
- All significant past and present contributors to GNU ELPA packages must sign the FSF copyright assignment. source
- Copyright assignment
- Significant past and present contributors to GNU ELPA packages must assign copyright to the Free Software Foundation. source
- Dependency handling
- Emacs automatically downloads required dependencies when installing a package, stopping if a required dependency is unavailable. source
- Development archive
- GNU ELPA publishes a separate GNU-devel ELPA archive for development or bleeding-edge package versions. source
- Free software criterion
- A package’s core functionality must work on a system using only free software, subject to case-by-case exceptions. source
- Independent praise: built-in ecosystem
- Emacs Redux highlights that GNU ELPA packages such as cl-lib, eldoc and xref originated with Emacs development and integrate closely with the editor. source
- Independent praise: official status
- Emacs Redux describes GNU ELPA as the official Emacs package repository and notes that some packages are bundled with Emacs. source
- Independent security observation
- The Emacs manual says archive packages should be trusted because installing them can run code with the user's permissions, and recommends cryptographic signing to improve security. source
- Installation command
- Users can browse and install packages from inside Emacs with M-x list-packages. source
- Install location
- Installed packages are placed under the package-user-dir directory, which defaults to ~/.emacs.d/elpa/. source
- License policy
- Submitted packages must use a GPL-compatible license, ideally GPLv3 or later. source
- License policy
- Submitted packages must use a GPL-compatible license, with GPLv3 or later preferred. source
- Limit: contributor burden
- Emacs Redux reports that copyright paperwork, the ELPA repository workflow and the Emacs bug tracker discourage many outside contributors. source
- Limit: outages
- Reddit users reported GNU ELPA and related GNU sites being unreachable for hours during a June 2024 incident, with packet loss and 443 errors. source
- Limit: package freshness complaint
- A Reddit user reported that an older Magit package in ELPA caused compatibility problems and that switching to MELPA resolved the installation issue. source
- Limit: refresh hangs
- A Reddit report describes package-refresh-contents hanging indefinitely on Debian 11 while accessing GNU and NonGNU ELPA, with IPv6 or site connectivity suspected. source
- Limit: smaller catalog
- Emacs Redux reported GNU ELPA hosting about 280 packages at the time, far fewer than MELPA's roughly 5,000 packages. source
- Local hosting
- The repository documentation describes deploying a locally hosted archive by generating archive files and serving the archive directory over HTTP. source
- Maintainer compromise risk
- GNU ELPA's contribution page states that a compromised package maintainer repository can create a security risk for users. source
Checked against the maker's pages on 15 Oct 2026.