bagisto
Open Source eCommerce & Multi-Vendor Marketplace Platform Built with Laravel for Enterprise-Scale Commerce, Supporting 10M+ SKUs
Runs with mockssource: GitHubhomepagePHPMITcommit 805b67013134
PHP, MIT licensed. The project labels itself: b2b ecommerce, blockchain ecommerce, ecommerce, ecommerce framework, ecommerce platform, hacktoberfest, headless commerce and laravel.
bagisto runs, with stand-ins for the services it depends on. An Argusic agent installed it in 27 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Bagisto 2.4.x is installed with Composer dependencies, all 200+ migrations applied, database seeded, Laravel development server serving the shop homepage at HTTP 200, and 172 Pest tests passing across 6 suites.
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 92 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.
- No MySQL or Redis available; no apt-get access (no root)5 minutes
- PHP 8.3+ not installed in container3 minutes
- Database seeder CategoryTableSeeder inserts root category translation without url_path (NOT NULL column)3 minutes
- Composer not installed1 minute
- Install time
- 27 minutes
- Cold machine to finish
- 32 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- curl -s -o /dev/null http://127.0.0.1:8001/ returned HTTP 200 serving 237KB HTML; 6 test suites passed: Core Unit (79/79), Customer Unit (32/32), DataGrid Unit (1/1), EUWithdrawal Feature (12/12), FPC Unit (24/24), Installer Feature (24/24), 172 tests, 267 assertions total
- Model tokens used
- 481,658
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Here's the final summary of what I found and fixed: **Problems encountered:** 1. **PHP 8.3+ not installed** — No PHP binary in the container. Fixed by downloading the `static-ph… 2. **Composer not installed** — Downloaded `composer.phar` 2.8.6. `composer install` completed succ… 3. **No MySQL or Redis** — Neither MySQL/MariaDB nor Redis was installed. Stood up **Dolt** (`dolth… 4. **Seeder missing `url_path`** — The root category translation insert in `packages/Webkul/Install… exec /bin/sh -lc 'echo "Bagisto install and verification complete. Total elapsed approx 37 minutes."' in… succeeded in 0ms: Bagisto install and verification complete. Total elapsed approx 37 minutes. tokens used 481,658
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
- Installed in 27 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.12 |
Topics (from GitHub)
b2b-ecommerceblockchain-ecommerceecommerceecommerce-frameworkecommerce-platformhacktoberfestheadless-commercelaravellaravel-applicationlaravel-ecommercelaravel-packagemulti-tenancy-pluginmulti-tenantmulti-vendor-ecommercemultivendor-ecommercenft-marketplaceopen-sourceopensource-ecommercephpphp-ecommerce
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/bagisto)Questions
- Does bagisto run?
- bagisto runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 27 minutes, hitting 4 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. One attempt is 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.12: 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?
- 27 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?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for bagisto?
- 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.