Sylius
Headless open-source eCommerce platform on top of PHP/Symfony/API Platform
Runssource: GitHubhomepagePHPMITcommit 38588aff004e
PHP, MIT licensed. The project labels itself: api, api ecommerce, ecommerce, ecommerce platform, framework, hacktoberfest, headless and headless ecommerce.
Sylius runs. An Argusic agent installed it in 32 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
With a rootless PHP 8.3.6+MariaDB 10.11.11 bootstrap, Sylius installs end to end, the Symfony shop and API serve real responses (shop 200, API collection of 87 products, admin login 200), all 686 API/functional tests pass with one upstream skip, PHPStan reports no errors, and frontend assets compile via encore.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- PHP 8.3, Composer, MySQL and Yarn were not present in the container and no apt/root was available; the README stack expects php 8.3 Docker image + MySQL18 minutes
- yarn install and yarn encore failed with engine error node>=22 vs node 18.19.1 (package.json engines, engineStrict)6 minutes
- vendor/bin/ecs (EasyCodingStandard 13.1.2) fatals at startup under PHP 8.3: bundled squizlabs/php_codesniffer Tokens.php references T_AND_EQUAL/T_POW/T_COMMENT etc. that are undefined at class load, and the parallel worker also fails; --no-parallel option does not exist in this version6 minutes
- sylius:install on a pre-created empty DB rolled back leaving no sylius_currency table; also first run hit No such file session.save_path (/var/lib/php/sessions)4 minutes
- phpstan analyse failed: PHPDoc @var DateTimeInterface not subtype of native DateTimeImmutable in ProductLowestPriceBeforeDiscountProcessor.php:830.5 minutes
- Install time
- 32 minutes
- Cold machine to finish
- 43 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- php -S 127.0.0.1:8010 -t public then curl /en_US/ returned 200 (title Fashion Web Store, built css/js referenced), /api/v2/docs 200, /admin/login 200, /api/v2/shop/products 200 JSON hydra:totalItems 87; vendor/bin/phpunit tests/Api tests/Functional -> OK 686 tests, 2074 assertions, 1 skipped (upstream); vendor/bin/phpstan analyse -> [OK] No errors; curl of compiled shop css/js 200
- Model tokens used
- 3,155,168
- Exact commit tested
- 38588aff004e
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- **Frontend:** `yarn install --ignore-engines` (engines pins node>=22; here node is 18.19.1) and `…
- **App verified live:** `php -S 127.0.0.1:8010 -t public`; `/en_US/` returned 200 with `<title>Fas…
- **Tests:** full `tests/Api tests/Functional` suite → `686 tests, 2074 assertions, OK, 1 skipped` …
- **Static analysis:** `phpstan analyse` failed on one annotation, fixed (`@var DateTimeInterface` …
- **ECS:** could not run: bundled PHP_CodeSniffer inside ECS 13.1.2 dies at class-load with `Undefi…
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT:{\"install_succeeded\": true, \"launch_succeeded\": true, \"insta…
succeeded in 0ms:
Done. One line as required:
tokens used
3,155,168
Done. One line as required:Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 32 minutes to install, slower than the median of the 61 comparable projects Argusic has measured.
Of the 62 api projects Argusic has installed and timed, Sylius was the 61st fastest to reach a running state, and 37 of 62 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
apiapi-ecommerceecommerceecommerce-platformframeworkhacktoberfestheadlessheadless-ecommercephprest-apirestful-apishopshopping-cartsyliussymfonysymfony-bundle
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/sylius)Questions
- Does Sylius run?
- Yes. Sylius runs. Argusic installed and launched it on a clean machine in 32 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test Sylius?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 38588aff004e. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Sylius?
- The run that produced this verdict cost $0.61: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Sylius take to install?
- 32 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does Sylius need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Sylius?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does Sylius compare with the alternatives?
- Of the 62 api projects Argusic has installed and timed, Sylius was the 61st fastest to reach a running state, and 37 of 62 reached one at all.
- Where is the evidence for Sylius?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.