goshop

E-Commerce system via Golang and ReactJS

Runssource: GitHubGoMITcommit 3990165dd9b4

Go, MIT licensed. The project labels itself: authentik integrations, ddd, domain driven design, ecommerce, gin, golang, gprc and postgresql.

goshop runs. An Argusic agent installed it in 6 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Go 1.26.0 installed, project builds and all 41 Go packages (1020 tests) pass, web frontend builds and all 7 web tests pass, compiled binary starts and exits with expected DB-connection error proving the code compiles and runs

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.09 (measured)
recorded runs
1
last tested
stars
412
forks
89
open issues
9
watchers
3
size
2 MB
created
last push

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.

Time lost to each failure while testing goshop, 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.

  • Web frontend vitest/vite build fails with Node.js 18 (need Node 22+)2 minutes
  • Go compiler not found in environment1 minute
  • Missing config.yaml (config_test.go expects one)0.5 minutes
Install time
6 minutes
Cold machine to finish
7 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
Go test suite: 1020 individual test cases across 41 packages all PASS, exit 0. Web frontend: `npm run build` produces dist/ (1708 modules), `npm test` passes 7/7 tests. Backend binary compiled to /tmp/goshop (67 MB). Server fails at startup only because no Postgres/Redis are available (expected in this environment).
Model tokens used
112,541
Exact commit tested
3990165dd9b4
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.

- **Web frontend**: Node.js 18 was too old for vite/vitest v5 (needs Node 22+). Installed `nvm` + N…
- **Backend binary**: Compiles successfully (67 MB static binary). Attempting to launch fails becau…
- **Integration tests**: Skipped because Docker is not available (required for testcontainers). The…
tokens used
112,541
Here's the full summary of what I found and did:
Key details:
- **Go**: Downloaded `go1.26.0` tarball (~64 MB), extracted to `/home/runner/go-install/go`. All 41…
- **Config**: The one test failure (`TestLoadConfig_PopulatesFromYAML`) was fixed by copying `confi…
- **Web frontend**: Node.js 18 was too old for vite/vitest v5 (needs Node 22+). Installed `nvm` + N…
- **Backend binary**: Compiles successfully (67 MB static binary). Attempting to launch fails becau…
- **Integration tests**: Skipped because Docker is not available (required for testcontainers). The…

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 6 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 MIT, 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.
  • A quick evaluation: it was running 6 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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.09

Topics (from GitHub)

authentik-integrationsddddomain-driven-designecommercegingolanggprcpostgresqlrate-limitreactjsredisrestfulshopstripestripe-integrationswagger

Embed the badge

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

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

Questions

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

Discussion