saleor
Saleor Core: the high performance, composable, headless commerce API.
Runssource: GitHubhomepagePythonBSD-3-Clausecommit 5ff56489737c
Python, BSD-3-Clause licensed. The project labels itself: cart, checkout, commerce, composable, e commerce, ecommerce, graphql and headless.
saleor runs. An Argusic agent installed it in 40 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Saleor 3.24.0-a.0 dependencies installed via uv sync, PostgreSQL 16 running from extracted binaries, all 400+ schema migrations applied, 333 of 335 core/asgi/site tests passing, ASGI server boots and returns HTTP 200 on health endpoint
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.
- SQLite incompatible - Saleor requires PostgreSQL (django.contrib.postgres)10 minutes
- libmagic.so not found - python-magic ImportError on startup5 minutes
- pywatchman dev dependency fails to compile - no python3.12-dev headers5 minutes
- Install time
- 40 minutes
- Cold machine to finish
- 42 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pytest --ds=saleor.tests.settings --nomigrations --reuse-db on saleor/core/tests/ saleor/asgi/tests/ saleor/site/tests/ returned 333 passed, 1 failed (search vector), 1 error (search vector); uvicorn saleor.asgi:application returned 200 on /health/
- Model tokens used
- 1,016,724
- Exact commit tested
- 5ff56489737c
- 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.
- Deselected tests are `cleardb` and `create_fake*` commands that need a populated database. **Server**: `uvicorn saleor.asgi:application` boots and returns `200 OK` on `/health/`. exec /bin/sh -lc 'start_epoch=1790354800; end_epoch=1790366286; total_seconds=$((end_epoch - start_epoch… succeeded in 0ms: Elapsed: ~191 minutes Let me compute the elapsed time properly and clean up: exec /bin/sh -lc 'pkill -f "manage.py" 2>/dev/null; pkill -f "uvicorn" 2>/dev/null; pkill -f "postgres" … exited 143 in 0ms: tokens used 1,016,724
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 40 minutes.
- Recovered from all 3 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 BSD-3-Clause, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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)
cartcheckoutcommercecomposablee-commerceecommercegraphqlheadlessheadless-commercemultichannelomsorder-managementpaymentspimpythonshopshopping-cartstore
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/saleor)Questions
- Does saleor run?
- Yes. saleor runs. Argusic installed and launched it on a clean machine in 40 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test saleor?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5ff56489737c. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test saleor?
- The run that produced this verdict cost $0.28: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does saleor take to install?
- 40 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 saleor need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing saleor?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for saleor?
- 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.