GNU ELPA

GNU ELPA alternatives

GNU ELPA is the default package repository for GNU Emacs. It lists Emacs Lisp packages with versions and descriptions, and lets you browse or install them from Emacs.

These alternatives serve other language ecosystems or provide self-hosted repository tools. The key difference is package ecosystem and hosting model; choose based on the software you need to distribute.

  1. PPyPI: the Python Package IndexAPIOpenFree

    PyPI is a public repository for Python software, helping people find and install packages shared by the Python community. It has web and API access, runs across Linux, macOS and Windows, and is also available for self-hosting. Unlike GNU ELPA's Emacs-focused archive and GPL-compatible policy, PyPI serves the Python ecosystem and uses a freemium model with a free plan and paid options.

    Trade-off: You leave GNU ELPA's direct Emacs package workflow and move to Python's ecosystem; paid options start at $5/user/mo. Suits: Teams distributing or installing Python packages across common desktop and server systems.

  2. LLuaRocks: a package registry for LuaAPIOpenFree

    LuaRocks distributes Lua packages in .rock and .rockspec formats. It supports dependency resolution and offline installation, with API access and self-hosted use on Linux, macOS, Windows and other listed Unix systems. GNU ELPA instead delivers Emacs Lisp packages through Emacs. LuaRocks is free, but its package formats and ecosystem are for Lua rather than Emacs.

    Trade-off: You give up GNU ELPA's Emacs archive and package-install workflow for Lua-specific formats and tools. Suits: Lua users who need dependency handling or offline package installation.

  3. Ppypiserver: a minimal private Python indexAPIOpenFree

    pypiserver is an open-source, minimal PyPI-compatible server for uploading and downloading Python packages. It serves packages from regular directories, including wheels, bdists and eggs, and works with pip, easy_install and twine. Uploads can use packaging tools or scp. Compared with GNU ELPA's central Emacs archive, it is a small self-hosted Python index with no paid plan.

    Trade-off: It is limited to Python package formats and basic index serving, not GNU ELPA's Emacs package pages and archive workflow. Suits: People needing a simple private Python package index on their own server.

  4. Aaptly: controlled Debian repositoriesAPIOpenFree

    aptly manages Debian repositories by mirroring remote sources, maintaining local repositories, taking immutable snapshots and publishing them through a CLI or HTTP REST service. It can pull package versions with dependencies and roll back to earlier fixed sets. GNU ELPA distributes Emacs Lisp packages, while aptly targets Debian packages and repeatable system installations. It is free and self-hosted.

    Trade-off: You switch from Emacs package installation to Debian repository management, and aptly is self-hosted rather than web-based. Suits: Linux teams that need snapshots, mirrors, dependency pulls and controlled Debian releases.

  5. MCMaven Central: the public Java repositoryAPIOpenFree

    Maven Central is a public distribution platform for release-ready open-source software in the Java ecosystem. It is the default repository for Apache Maven, SBT and other build systems, and also works with Ant/Ivy and Gradle. Its website supports component search and browsing. GNU ELPA focuses on Emacs packages; Maven Central focuses on Java components and offers a free plan.

    Trade-off: You lose GNU ELPA's Emacs integration and move to Java build systems; the listed service is web and API based. Suits: Java teams using Maven, SBT, Gradle or related build tools.

  6. PPackagist: the default Composer package repositoryAPIOpenFree

    Packagist is the default Composer repository for PHP. It aggregates public PHP packages that anyone can install, and publishing starts by submitting a public repository URL that Packagist periodically crawls. GNU ELPA accepts Emacs packages under GPL-compatible rules and builds its archive, while Packagist centers on public PHP code and Composer. It is free with web and API access.

    Trade-off: You move from GNU ELPA's Emacs archive and submission rules to Composer and Packagist's public PHP workflow. Suits: PHP developers publishing or installing public packages with Composer.

  7. JJSR: a modern JavaScript and TypeScript registryAPIOpenFree

    JSR is an open-source registry for JavaScript and TypeScript, licensed under MIT. It accepts TypeScript source, generates documentation and declaration files, and transpiles code for cross-runtime compatibility. Packages are distributed as web-standard ECMAScript modules. GNU ELPA provides Emacs Lisp packages with Emacs installation; JSR instead serves web and API users in the JavaScript and TypeScript ecosystem.

    Trade-off: You give up GNU ELPA's Emacs package archive and use JavaScript or TypeScript modules instead. Suits: JavaScript or TypeScript teams that want generated docs and cross-runtime modules.

  8. RUR-universe: publishing and discovery for R softwareAPIOpenFree

    R-universe is rOpenSci's platform for publishing and discovering research software in R. It offers a searchable catalog of R software, articles and datasets, with R-specific indexing and ranking, plus detailed package pages and rendered material. Users can run personal CRAN-like repositories with or without publishing on CRAN. GNU ELPA instead serves Emacs Lisp packages.

    Trade-off: You switch from Emacs Lisp and GNU ELPA's Emacs workflow to R packages and personal repository hosting. Suits: R users and researchers who need package discovery or a personal CRAN-like repository.

More near it on Package Registries

  1. 1
    B
    Bioconductorbioconductor.org

    Bioconductor develops open-source software for precise, repeatable analysis of biological data.

    7.7 APIOpenFree Free tier
  2. 5
    N
    npmnpmjs.com
    6.6 APIOpenFree Free tier · from $7/mo
  3. 7
    IP
    Inedo ProGetinedo.com

    ProGet is a self-hosted, cross-platform package and container repository for keeping packages and Docker containers in one place, scanning vulnerabilities, and…

    6.6 APIOpenFree Free tier · from $2,395/yr
  4. 8
    N
    NuGetnuget.org

    NuGet is the package manager for .NET, providing tools to create, share, and consume packages.

    6.4 APIOpenFree Free tier
  5. 9
    C
    Conanconan.io
    6.4 APIOpenFree Free tier
  6. 10
    RO
    RubyGems.orgrubygems.org

    RubyGems.org is the Ruby community's gem hosting service.

    6.4 APIOpenFree Free tier
  7. 12
    C
    CocoaPodscocoapods.org

    CocoaPods is a dependency manager for Swift and Objective-C Cocoa projects.

    6.4 APIOpenFree Free tier
  8. 13
    NE
    NonGNU ELPAelpa.nongnu.org

    NonGNU ELPA is an Emacs Lisp package archive for extending GNU Emacs.

    6.4 APIOpenFree Free tier
  9. 14
    O
    opamopam.ocaml.org

    opam is a source-based package manager for OCaml.

    6.3 APIOpenFree Free tier
  10. 15
    C
    CPANcpan.org
    6.3 APIOpenFree Free tier
  11. 17
    R
    Rr-project.org
    6.1 APIOpenFree Free tier
  12. 18
    D
    devpidevpi.net

    devpi is a Python package index server and packaging, testing, and release tool.

    6.0 APIOpenFree Free tier
  13. 21
    M
    MELPAmelpa.org

    MELPA is a collection of package.el-compatible Emacs Lisp packages built automatically from upstream source using recipes.

    6.0 APIOpenFree Free tier

Questions

Is GNU ELPA free?

Yes. GNU ELPA is free, has a free plan and no free trial. It is open source and runs as a self-hosted or web archive.

What does GNU ELPA require from contributors?

Submitted packages need GPL-compatible licensing, package conventions and a maintainer email. Significant past and present contributors must assign copyright to the FSF.

Can I host a package archive myself?

GNU ELPA documentation describes generating archive files and serving the archive directory over HTTP.

How does GNU ELPA install packages?

In Emacs, browse with M-x list-packages or install with package-install. Emacs downloads required dependencies when available and places packages under package-user-dir by default.

Are GNU ELPA packages safe to run?

GNU ELPA warns that installed packages can execute arbitrary code with your permissions, and that a compromised maintainer repository can create security risk.