pre-release, built in the open

18x faster warm installs than Composer. Byte-identical vendor/.

An extremely fast, Composer-compatible PHP installer, written in Rust. It reads your composer.json and composer.lock unchanged and writes the same vendor/, byte for byte, in a fraction of the time on every install that is not bound by the network.

Early, built in the open. phpm install is byte-identical to Composer on 98.1% of a 312-project nightly sweep, and its warm installs beat Composer's on every project measured on Linux and macOS. Windows isn't supported yet (open issues, help welcome). It installs from a lockfile only: no update or require yet. Every phase, decision and benchmark behind those numbers is public: start at phases.

18x
warm install, Laravel skeleton — 222 ms vs Composer's 4.179 s
4.5ms
no-op install — Composer re-validates a satisfied lockfile in 1.606 s
identical
vendor/, bytes and file modes, on every pinned fixture
benchmarks

Warm install, Laravel skeleton

109 packages, M1 Pro, APFS, Composer 2.10.3, hyperfine, every tool measured in the same session. Lower is faster.

Cold install is network-bound and measured separately: on the ytmate fixture phpm's cold median is 11.65 s against riff's 13.19 s, a tie within the noise. On Linux (GitHub ubuntu-latest, ext4) phpm was 14x faster than Composer warm and 633x on a no-op at the Phase 01 gate. vendor/ is identical to Composer's for vivacity and phpm; riff differs on 4 files and viv on every file mode.

Real apps, not just a skeleton

Same machine, with each fixture's own scripts and plugins on (results).

FixtureComposer warmphpm warmSpeed-up Composer no-opphpm no-opSpeed-up
Bedrock (WordPress)4.496 s319 ms14.1x 1.204 s4.7 ms256x
drupal/recommended-project15.119 s1.973 s7.7x 1.260 s5.4 ms233x

Both fixtures install fully natively — no Composer fallback for any step. Full real-world benchmark suite (40 open-source apps, three OSes) is Phase 05, in progress — results land here as they publish.

why phpm

Why a second tool, when Composer is good

Composer is good: a lockfile, parallel downloads, one blessed registry, a respected maintainer team. The question was never "is Composer slow" — it is "where is it slow enough that someone would install a second tool."

01

It never breaks a project

Every competitor either refuses plugins, emulates a few, or breaks silently. phpm installs natively when it can prove the result is identical to Composer's, and hands the rest to real Composer when it cannot — --explain says which. A user should never be worse off for having tried it.

02

Compatibility is published, not claimed

A nightly sweep diffs phpm's vendor/ against Composer's across hundreds of real projects and publishes the number, the way Ruff published ">99.9% Black-compatible." See Compatibility.

03

It is built for where installs multiply now

Agents run installs in CI, in containers, and in parallel git worktrees, each wanting its own vendor/. With a shared store, a new worktree's vendor/ costs a fraction of a second and almost no disk.

compatibility

Published nightly, not claimed

A nightly sweep installs phpm and Composer side by side across 330 pinned open-source PHP projects and diffs vendor/ byte for byte, modes included — live results and methodology.

ModeIdenticalRatioGate
Plugins and scripts off306 / 31298.1%95% — passed
Plugins and scripts on
(Composer fallback included)
267 / 28195.0%—

The sweep is also how real bugs get found before users hit them: it caught a case where, on filesystems without copy-on-write cloning, a plugin writing into a hard-linked file could corrupt the shared package store for every later install. phpm now copies instead of hard-linking whenever scripts or plugins will run.

vendor/ is also byte-identical, bytes and file modes, on every one of the project's own pinned fixtures (Laravel, Symfony demo, Monica, Bedrock, drupal/recommended-project, and two production apps), including the optimised class map.

Open the live sweep
install

Install

Prebuilt binaries for macOS and Linux are on every GitHub release. Windows isn't supported yet; the gaps are filed as issues.

macOS and Linux
$ curl -LsSf https://github.com/speedsharmaai/phpm/releases/latest/download/phpm-installer.sh | sh
Homebrew or source
$ brew install speedsharmaai/phpm/phpm
$ cargo install --locked --git https://github.com/speedsharmaai/phpm --tag v0.1.1 phpm

Then run it against a real project:

terminal
$ cd /path/to/your/php/project
$ phpm install --explain
Installing 109 packages...
109 native, 0 handed to Composer. vendor/ identical.

--explain prints, per package, whether it was installed natively or handed to Composer and why. Plain phpm install otherwise behaves like composer install: --no-dev, --no-scripts, --no-plugins, --optimize-autoloader / -o, --classmap-authoritative / -a all work.