Yes. yas runs. Argusic installed and launched it on a clean machine in 42 minutes, hitting 3 errors on the way, and recorded the session.

How did Argusic test yas?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 179e813568c3. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test yas?

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

How long does yas take to install?

42 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.

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

What goes wrong when installing yas?

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 yas?

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.

yas

YAS: Yet Another Shop, a sample microservices project in Java

Runssource: GitHubJavaMITcommit 179e813568c3

Java, MIT licensed. The project labels itself: docker, ecommerce, hacktoberfest, java, keycloak, kubernetes, microservices and sample project.

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

18 Java backend modules (common-library, cart, customer, inventory, location, media, order, payment-paypal, payment, product, promotion, rating, tax, webhook, backoffice-bff, storefront-bff, sampledata, delivery) compile with JDK 25 and Maven 3.9.9 and pass 374 unit tests using H2 in-memory databases; storefront and backoffice Next.js 14 frontends build with npm and serve HTTP 200 on their respective ports;
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.14 (measured)
recorded runs: 1
last tested: 2026-10-05
stars: 1,987
forks: 735
open issues: 156
watchers: 35
size: 90 MB
created: 2022-01-18
last push: 2026-06-12

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

No JDK or Maven installed in container4 minutes
search module tests fail - Docker Testcontainers require Keycloak and Kafka containers
recommendation module tests fail - Docker Testcontainers require Kafka

Install time: 42 minutes
Cold machine to finish: 43 minutes
Errors hit and fixed: 3 hit, 3 fixed with no human help
How the result was proved: mvn test -pl '!search,!recommendation' returned BUILD SUCCESS (374 tests passed, 0 failures, 0 errors, 3 skipped across 18 modules); storefront: curl -s -o /dev/null -w '%{http_code}' localhost:3000 returned 200; backoffice: curl -s -o /dev/null -w '%{http_code}' localhost:3001 returned 200; npm run build for both storefront and backoffice completed with no errors
Model tokens used: 140,507
Exact commit tested: 179e813568c3
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.

2026-10-05T01:58:41.804344Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce…
Alright, let me now produce the final ARGUSIC_RESULT.
exec
/bin/sh -lc 'date -u +%s' in /work/repo
 succeeded in 0ms:
1791165527
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 4…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 42, "errors": [{"msg": "No…
tokens used
140,507

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

Took 42 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.
Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 12 docker projects Argusic has installed and timed, yas was the 11th fastest to reach a running state, and 9 of 12 reached one at all.

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

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	1/3	Runs	100.00	0.14	2026-10-05 01:59 UTC

Topics (from GitHub)

docker ecommerce hacktoberfest java keycloak kubernetes microservices sample-project shop spring-boot

Embed the badge

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

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

Questions

Does yas run?: Yes. yas runs. Argusic installed and launched it on a clean machine in 42 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test yas?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 179e813568c3. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test yas?: The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does yas take to install?: 42 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 yas need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing yas?: 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.
How does yas compare with the alternatives?: Of the 12 docker projects Argusic has installed and timed, yas was the 11th fastest to reach a running state, and 9 of 12 reached one at all.
Where is the evidence for yas?: 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.

yas