Yes. bagisto runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 6 errors on the way, and recorded the session.

How did Argusic test bagisto?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 805b67013134. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test bagisto?

The run that produced this verdict cost $0.52: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does bagisto take to install?

8 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 bagisto need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing bagisto?

6 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.

Where is the evidence for bagisto?

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.

bagisto

Open Source eCommerce & Multi-Vendor Marketplace Platform Built with Laravel for Enterprise-Scale Commerce, Supporting 10M+ SKUs

Runssource: GitHub homepagePHPMITcommit 805b67013134

PHP, MIT licensed. The project labels itself: b2b ecommerce, blockchain ecommerce, ecommerce, ecommerce framework, ecommerce platform, hacktoberfest, headless commerce and laravel.

bagisto runs. An Argusic agent installed it in 8 minutes and hit 6 errors on a clean machine with no GPU, and the whole session was recorded.

Bagisto 2.4.x running on static PHP 8.3.28 + extracted MySQL 8.0.46 locally. composer install completed, artisan bagisto:install --no-interaction ran all 260+ migrations and seeded data, server responds HTTP 200 on / and 302 redirect on /admin, six test suites total 259+ passed, 30 pre-existing Flat.php indexer failures in payment packages.
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 94.3 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 94.3 / 100
cost of the verifying run: $0.52 (measured)
recorded runs: 2
last tested: 2026-11-02
stars: 28,350
forks: 3,381
open issues: 29
watchers: 173
size: 419 MB
created: 2018-09-10
last push: 2026-11-06

Subject data from GitHub, linked at the top of this page, refreshed 2026-11-09. 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.

Time lost to each failure while testing bagisto, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

MySQL 8.0 not pre-installed4 minutes
PHP 8.3+ not pre-installed in container2 minutes
SQLite incompatible with migrations (DROP FOREIGN KEY by name)1 minute
MySQL server stopped when parent shell exited1 minute
Composer not pre-installed
30 payment gateway tests failing (Stripe, PayGlocal, PayU, Razorpay) — all in Product/Helpers/Indexers/Flat.php:188 (pre-existing indexer bug, not caused by install)

Install time: 8 minutes
Cold machine to finish: 16 minutes
Errors hit and fixed: 6 hit, 5 fixed with no human help
How the result was proved: curl -s -o /dev/null -w %{http_code} http://localhost:8001/ returned 200, curl to /admin returned 302; Pest test suite ran 259+ passed (Core 79, Customer 32, FPC 111, DataGrid 1, EUWithdrawal 12, Installer 24) with 30 pre-existing Flat.php indexer failures
Model tokens used: 153,001
Exact commit tested: 805b67013134
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.

echo "--- Done ---"' in /work/repo
exec
/bin/sh -lc 'kill %2 %1 2>/dev/null; killall mysqld 2>/dev/null; echo "done"' in /work/repo
 succeeded in 0ms:
done
All verified. Here is the final report:
2026-11-02T11:22:35.020753Z ERROR codex_core::session: failed to record rollout items: thread 01a19…
2026-11-02T11:22:35.020788Z ERROR codex_core::session: failed to record rollout items: thread 01a19…
2026-11-02T11:22:35.020809Z ERROR codex_core::session: failed to record rollout items: thread 01a19…
tokens used
153,001
All verified. Here is 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 8 minutes.
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

Hit 6 errors during setup, 1 of which were not solved.

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 8 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

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Runs	96.67	0.52	2026-11-02 11:22 UTC
Argusic Runner	1/3	Runs with mocks	92.00	0.12	2026-09-25 16:47 UTC

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/bagisto.svg)](https://argusic.com/subject/bagisto)

Questions

Does bagisto run?: Yes. bagisto runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test bagisto?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 805b67013134. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test bagisto?: The run that produced this verdict cost $0.52: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does bagisto take to install?: 8 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 bagisto need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing bagisto?: 6 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.
Where is the evidence for bagisto?: 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.