Composer and Packagist in the ecosystem #

Contents #

1. Why Composer
2. The se7enxweb vendor
3. Composer or Git clones
4. Publishing on Packagist
5. Packages in the administration

Why Composer #

"Exponential 6.0.x specifically requires the php package manager called Composer" (README.md). Composer "installs the required Zeta Components php libraries and the extensions listed in composer.json" (README.md, "Requirements"). Since 6.0.15 those libraries are the expcomponents, Exponential's fork of the Zeta Components (se7enxweb/expcomponents-*). Without composer install, the software does not run.

The se7enxweb vendor #

• The kernel is se7enxweb/exponential; extensions, themes, servers and forks are se7enxweb/<name>.
• "On Packagist the vendor se7enxweb has 219 packages", counted on 18 October 2026 (https://packagist.org/packages/list.json?vendor=se7enxweb, The extension ecosystem).
• Third-party packages also take part: for example Nexus requires netgen/layouts-core (The Platform line).

Composer or Git clones #

"Every package is a GitHub repository under se7enxweb and a Composer package; composer require or a Git clone installs it" (Releases and version numbers). Git clones make it easy to update and to contribute fixes (Develop with Git, Getting the code).

Publishing on Packagist #

For your own package: a composer.json, a public repository, a Packagist entry and a webhook so that Packagist sees new tags (Composer and Packagist, The Packagist webhook). Not every extension has a composer.json yet; adding them is one of the roadmap's calls for volunteers (Roadmap).

Packages in the administration #

"Setup > Updates and packages, from the ezupdate extension, finds, checks and installs Composer packages from package servers" (Roadmap); see Update with Git.

Related pages #

• Packages
• How packages are versioned
• Composer and Git on servers
• PHP and Composer standards
• Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.