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 227 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Saleor runs in this container: Postgres 16, Redis 7.4, and libmagic were stood up rootlessly; migrations complete; the Django/GraphQL API answered HTTP 200 on /graphql/ for shop, products, and tokenCreate queries, authenticated attributeCreate/attributeUpdate mutations (errors:[]) persisted to Postgres, the Celery worker connected to Redis and became ready, and 233 pytest tests across product, GraphQL product queries...
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.
- python-magic import failed: could not find libmagic (system lib absent, /usr unwritable)8 minutes
- pytest suite killed by cgroup OOM under parallel xdist workers (oom_kill 2) on 1GB RAM/8GB cgroup7 minutes
- Interactive `manage.py shell` imported vendored django.contrib.auth before saleor.settings could install Saleor apps, crashing with RuntimeError5 minutes
- pywatchman build failed: Python.h not found (missing python3-dev headers on system Python)3 minutes
- Celery worker connected to amqp://[email protected]:5672 instead of Redis because CELERY_BROKER_URL (redis://localhost:6379/1) was unset in the tool environment2 minutes
- Install time
- 227 minutes
- Cold machine to finish
- 45 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- pytest (8+113+69+43 = 233 passed, 0 failed) across product/units, GraphQL product queries, GraphQL draft-order mutations, and file validators; plus POST /graphql/ returned HTTP 200 for shop query, tokenCreate JWT auth, attributeCreate/Update mutations with errors:[] confirmed in Postgres; celery worker reported 'ready' connected to redis://127.0.0.1:6379/1
- Model tokens used
- 2,347,324
- 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
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 2, 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.
- Verified: Django check, migrate (OK), populatedb, GraphQL API queries and authenticated mutations…
**Verified commands**
- `python manage.py check` → `System check identified no issues`
- `migrate` → `OK` (290 order migrations, 13 auth, etc. applied)
- `curl POST /graphql/` → HTTP 200, `{"data":{"__typename":"Query"}}`
- `tokenCreate` mutation → HTTP 200, real RS256 JWT; `attributeCreate`/`attributeUpdate` mutations …
- `celery worker` → `Connected to redis://127.0.0.1:6379/1`, `celery@... ready.`
- pytest: `test_generate_and_set_variant_name.py` 8 passed; `queries/test_product_query.py` 113 pas…
- GitHub repo untouched: `git status` clean
**Notes**
- `3:47` below was computed from the recorded start time (15:05, after env/README reconnaissance) t…
- All services were stood up rootlessly inside the container (system packages unavailable); no real…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 227 minutes.
- 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 BSD-3-Clause, as reported by its host.
- Measured 2 times, so the result is not a one-off.
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 227 minutes, hitting 5 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. 2 attempts are 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.53: 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?
- 227 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?
- 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.
- Where is the evidence for saleor?
- 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.