Packages / composer
APT repository · deb.freshdeb.com/composerprinted 28 Oct 2026, 04:08 UTC
composer
Composer, the dependency manager for PHP, as the composer.phar upstream releases, built from source. One release line for Debian 12 and 13, Ubuntu 22.04, 24.04 and 26.04 on amd64 and arm64.
latest 2.10.3getcomposer.orgupstream sourcepackaging
Componentmain
follows every upstream release, minors and majors included. Currently 2.10.3.
Not published yet. The first composer release is being built. These commands will work once it lands at deb.freshdeb.com/composer; the versions shown are the ones package.yaml will publish.
1Trust the signing key (once per machine)
sudo install -d -m 0755 /etc/apt/keyrings curl -fsSL https://deb.freshdeb.com/freshdeb-archive-keyring.gpg \ | sudo tee /etc/apt/keyrings/freshdeb-archive-keyring.gpg >/dev/null
Fingerprint 3BBD F03A 9C0B F890 F8CA 9510 7595 CC55 468F 3161. How to verify.
2Add the source
sudo tee /etc/apt/sources.list.d/freshdeb-composer.sources >/dev/null <<EOF
Types: deb
URIs: https://deb.freshdeb.com/composer
Suites: $(. /etc/os-release && echo $VERSION_CODENAME)
Components: main
Signed-By: /etc/apt/keyrings/freshdeb-archive-keyring.gpg
EOFWith auto, the shell reads the codename from /etc/os-release on the machine you paste this into.
3Install
sudo apt update && sudo apt install composer
apt policy composer # expect 2.10.3-1+freshdeb~…Already on the distribution's composer? The freshdeb version sorts higher, so apt upgrade moves you over in place. Config and data stay where Debian put them.
Compared with Debian's package
Debian's packaging decides where things go: package names, paths, users, services and how upgrades behave. The build follows upstream's own release builds wherever Debian's differs.
- Build
composer.phar, built from the release's source with upstream'sbin/compileand the dependencies incomposer.lock. Apart from self-update, it is byte-for-byte upstream's released phar.- Debian's build
- Installs Composer's sources against about 20 Debian-packaged PHP libraries, which older releases don't have in the versions Composer needs.
- Updates
composer self-updateis turned off: apt updates Composer.- Layout
- Debian's:
/usr/bin/composer, bash completion, the man page and the documentation. It depends only onphp-cli.
Packing list
Every release line of composer and the distributions it's built for. Each line is its own APT component and only gets the releases it follows (main: every upstream release, minors and majors included). After upstream end of life it stops building but stays installable. Hatched cells have no build: usually that distribution already ships the same or a newer version itself.
| Line | Component | Current | bookwormDebian 12 | trixieDebian 13 | jammyUbuntu 22.04 | nobleUbuntu 24.04 | resoluteUbuntu 26.04 | Support |
|---|---|---|---|---|---|---|---|---|
| main | main | 2.10.3 | built: 2.10.3-1 | built: 2.10.3-1 | built: 2.10.3-1 | built: 2.10.3-1 | built: 2.10.3-1 | – |
Versions follow <upstream>-<revision>+freshdeb~<distro>, distro being deb12, deb13, ubuntu22.04, ubuntu24.04 or ubuntu26.04, for amd64 and arm64. Published versions are never rebuilt or replaced.
Contents
- composer
- dependency manager for PHP
Origin
- Upstream
- github.com/composer/composerrelease tags pinned to commit hashes
- Debian packaging
- salsa.debian.org/php-team/pear/composerimported unmodified at d6918e9 (2.10.3-1, unstable)
- Our changes
- Per-line quilt patches under
patches/, plus overlays underoverlays/for bookworm, trixie, jammy, noble, resolute. - Built for
- bookworm, trixie, jammy, noble, resoluteamd64, arm64, built natively
- Notes
- packaging notes · package.yaml · report an issue
