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

How did Argusic test gokey?

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

What did it cost to test gokey?

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

How long does gokey take to install?

2.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 gokey need a GPU?

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

What goes wrong when installing gokey?

2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for gokey?

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.

gokey

A simple vaultless password manager in Go

Runssource: GitHubGoBSD-3-Clausecommit a5b5ea4b9bf9

Go, BSD-3-Clause licensed. The project labels itself: deterministic, ecc, ed25519, key generator, keychain, password generator, password manager and password store.

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

The gokey binary builds, all tests pass (2 test packages: gokey and rsa), the CLI generates passwords, raw keys, and PEM-encoded EC/RSA/ed25519/x25519 private keys from either a master password or an encrypted seed file, and the ci.yml workflow commands (prefer -p over -P, prefer -P over env, env var) all produce the expected output 'X"fZba:0S>'.
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.03 (measured)
recorded runs: 2
last tested: 2026-09-18
stars: 2,437
forks: 109
open issues: 8
watchers: 14
size: 0 MB
created: 2016-10-21
last push: 2026-07-10

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

Go not installed - downloaded go1.24.0.linux-amd64.tar.gz and extracted to /home/runner/go/go/1 minute
go vet: unkeyed fields in pkix.AlgorithmIdentifier struct literal at gokey.go:99 and :1020.2 minutes

Install time: 2 minutes
Cold machine to finish: 6 minutes
Errors hit and fixed: 2 hit, 2 fixed with no human help
How the result was proved: go build . && go build -o gokey ./cmd/gokey exited 0; go test ./... passed both packages with tests (gokey 9.006s, rsa 1.431s); ./gokey -p hunter2 -r test printed 'X"fZba:0S>' (matches CI expectation); ./gokey -p super-secret-master-password -t seed -o seedfile created a 256-byte encrypted seed; ./gokey ... -s seedfile -r example.com -t ec256/ec384/ec521/rsa2048/rsa4096/ed25519/x25519 all produced PEM output; ./gokey -t pass -l 20 produced 20-char password; ./gokey -t raw -l 16 produced 16 bytes; GOKEY_ROOT_PASS env var works; gofmt clean; go vet clean after fix
Model tokens used: 37,249
Exact commit tested: a5b5ea4b9bf9
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 2026-09-18, 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.

  -skip int
      number of bytes to skip from master seed file (default 0)
  -t string
      output type (can be pass, seed, raw, ec256, ec384, ec521, rsa2048, rsa4096, x25519, ed25519) …
  -u  UNSAFE: allow key generation without a seed
exit: 0
All verified. Here's the final report:
**Summary**: Go 1.24.0 had to be downloaded and installed as a prebuilt binary (no `go` was on the …
tokens used
37,249
All verified. Here's the final report:
**Summary**: Go 1.24.0 had to be downloaded and installed as a prebuilt binary (no `go` was on 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 2.1 minutes.
Recovered from all 2 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.
A quick evaluation: it was running 2.1 minutes after the clone.

Run history

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Runs	100.00	0.03	2026-09-18 01:26 UTC
Argusic Runner	1/3	Runs	100.00	0.01	2026-09-05 19:33 UTC

Topics (from GitHub)

deterministic ecc ed25519 key-generator keychain password-generator password-manager password-store password-vault rsa-key seed stateless

Embed the badge

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

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

Questions

Does gokey run?: Yes. gokey runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test gokey?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit a5b5ea4b9bf9. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test gokey?: The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does gokey take to install?: 2.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 gokey need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing gokey?: 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for gokey?: 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.