Sylius-Standard
Sylius app skeleton
Runssource: GitHubhomepagePHPMITcommit 6b580309567f
PHP, MIT licensed. The project labels itself: ecommerce, ecommerce framework, ecommerce platform, hacktoberfest, php, sylius, symfony and symfony application.
Sylius-Standard runs. An Argusic agent installed it in 9.5 minutes and hit 7 errors on a clean machine with no GPU, and the whole session was recorded.
The Sylius PHP backend boots successfully, its Symfony console commands work, its API responds correctly (200 on /api/v2/shop/products and /api/v2/docs), and its test suite passes; the frontend build failed because Node.js 18 does not meet Sylius's Node.js ^22 requirement, and the shop homepage errors because seed data is missing (no MySQL available to run the full install).
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 97.1 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 not found in container2.5 minutes
- MySQL connection refused — no MySQL server available2 minutes
- FOSRestBundle class not found — friendsofsymfony/rest-bundle missing from dependencies1.5 minutes
- Webpack entrypoints.json missing — frontend build incomplete1.5 minutes
- npm install failed — Node.js v18 does not meet Sylius requirement Node.js ^221 minute
- Composer not found0.5 minutes
- Install time
- 10 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 7 hit, 6 fixed with no human help
- How the result was proved
- vendor/bin/phpunit passed 4 tests with 6 assertions (3 deprecation warnings); curl against PHP built-in server returned HTTP 200 on /api/v2/shop/products (valid Hydra JSON-LD) and /api/v2/docs; HTTP 200 on /admin/login (full HTML rendered); HTTP 302 on root (redirect to shop)
- Model tokens used
- 568,890
- Exact commit tested
- 6b580309567f
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Time: 00:00.746, Memory: 215.00 MB OK, but there were issues! Tests: 4, Assertions: 6, Deprecations: 3. Let me clean up the PHP server and give a comprehensive test report exec /bin/sh -lc 'kill $(pgrep -f "php.*808[0-9]") 2>/dev/null; echo "Cleaned up servers"' in /work/repo succeeded in 0ms: Cleaned up servers All tests pass (4 tests, 6 assertions). Now let me compile the final report. tokens used 568,890 All tests pass (4 tests, 6 assertions). Now let me compile the final report.
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.
- Installed in 9.5 minutes, faster than the median of the 10 comparable projects Argusic has measured.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Hit 7 errors during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 11 ecommerce projects Argusic has installed and timed, Sylius-Standard was the 5th fastest to reach a running state, and 9 of 11 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.
- A quick evaluation: it was running 9.5 minutes after the clone.
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)
ecommerceecommerce-frameworkecommerce-platformhacktoberfestphpsyliussymfonysymfony-application
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/sylius-standard)Questions
- Does Sylius-Standard run?
- Yes. Sylius-Standard runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test Sylius-Standard?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6b580309567f. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test Sylius-Standard?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Sylius-Standard take to install?
- 9.5 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-Standard need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Sylius-Standard?
- 7 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does Sylius-Standard compare with the alternatives?
- Of the 11 ecommerce projects Argusic has installed and timed, Sylius-Standard was the 5th fastest to reach a running state, and 9 of 11 reached one at all.
- Where is the evidence for Sylius-Standard?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.