Argusic could not verify that go-recipes runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.

How did Argusic test go-recipes?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit a954f17ee3ef. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test go-recipes?

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

How long does go-recipes take to install?

0.1 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 go-recipes need a GPU?

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

What goes wrong when installing go-recipes?

Nothing did, in the recorded run: zero errors between clone and running.

Where is the evidence for go-recipes?

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.

go-recipes

🦩 Tools for Go projects

Could not verifysource: GitHubGoMITcommit a954f17ee3ef

Go, MIT licensed. The project labels itself: awesome, awesome list, benchmarking, code generation, code visualization, command line tool, compilers and data visualization.

Argusic could not get go-recipes running. An Argusic agent installed it in 0.1 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Go 1.23.4 installed; project builds without error; README generated from page.yaml via go generate; binary runs and exits successfully.
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 80 of 100 (the mean of this project's run scores).

At a glance

verdict: Could not verify
Argusic Score: 80 / 100
cost of the verifying run: $0.01 (measured)
recorded runs: 2
last tested: 2026-09-30
stars: 4,780
forks: 186
open issues: 24
watchers: 45
size: 24 MB
created: 2021-06-26
last push: 2026-09-09

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

Install time: under a minute
Cold machine to finish: 3 minutes
Errors hit and fixed: 0 hit, 0 fixed with no human help
How the result was proved: go build ./... exited 0, go generate ./... exited 0, built binary ran and exited 0, go vet ./... clean
Model tokens used: 14,075
Exact commit tested: a954f17ee3ef
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
Whether it works at all: this run verified nothing, so this page makes no claim either way

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

=== Check README generated ===
45
exec
/bin/sh -lc 'export PATH="/tmp/go/bin:$PATH" && cd /work/repo && go build -o /tmp/gorecipes . && /t…
 succeeded in 11ms:
exit code: 0
All checks pass. Here's the summary:
**ARGUSIC_RESULT:** {"install_succeeded":true,"launch_succeeded":true,"install_minutes":0.1,"errors…
tokens used
14,075
All checks pass. Here's the summary:
**ARGUSIC_RESULT:** {"install_succeeded":true,"launch_succeeded":true,"install_minutes":0.1,"errors…

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 0.1 minutes.
Nothing broke on the way: zero errors between clone and running.
Licensed MIT, as reported by its host.
Measured 2 times, so the result is not a one-off.

What did not, or is not known

An agent with no time limit did not get it running.

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	2/3	Unverified	80.00	0.01	2026-09-30 04:20 UTC
Argusic Runner	1/3	Unverified	80.00	0.02	2026-09-30 01:19 UTC

Topics (from GitHub)

awesome awesome-list benchmarking code-generation code-visualization command-line-tool compilers data-visualization developer-tools documentation go golang profiling static-analysis tests visualization

Embed the badge

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

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

Questions

Does go-recipes run?: Argusic could not verify that go-recipes runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test go-recipes?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit a954f17ee3ef. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test go-recipes?: The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does go-recipes take to install?: 0.1 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 go-recipes need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing go-recipes?: Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for go-recipes?: 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.