gopass
The slightly more awesome standard unix password manager for teams
Runssource: GitHubhomepageGoMITcommit e2dd748cdbe1
Go, MIT licensed. The project labels itself: git, go, gpg, hacktoberfest, password manager and security.
gopass runs. An Argusic agent installed it in 25 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
gopass builds, runs, and all 68 Go test packages pass with real GPG and age encryption backends.
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 93.5 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.
- gpg, gpg-agent, gpgconf binaries not found3 minutes
- gpg-agent could not start: hardcoded path /usr/bin/gpg-agent2 minutes
- Go compiler not found in PATH1 minute
- TestUpdateWorkflows failed: git user unset1 minute
- Install time
- 25 minutes
- Cold machine to finish
- 26 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- go test ./... exited 0; 68 packages all ok, 0 failures. ./gopass version returned 'gopass 1.17.0 (1e939616) go1.25.0 linux amd64'
- Model tokens used
- 122,300
- Exact commit tested
- e2dd748cdbe1
- 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.
3. **gpg-agent not found at `/usr/bin/gpg-agent`** -- Added `agent-program /tmp/gpginstall/usr/bin/… 4. **helpers/postrel test failed** -- `git config --global user.email / user.name` was unset. **Things skipped:** `make fmt` and `make codequality` fail because `keep-sorted` and `license-lint`… tokens used 122,300 Everything is passing. Here's the summary: **Errors and fixes:** 1. **Go not installed** -- Downloaded go1.23.0 tarball to `/tmp/go` and added to PATH. 2. **gpg, gpg-agent, gpgconf not installed** -- Extracted gpg, gpg-agent, gnupg-utils, dirmngr, and… 3. **gpg-agent not found at `/usr/bin/gpg-agent`** -- Added `agent-program /tmp/gpginstall/usr/bin/… 4. **helpers/postrel test failed** -- `git config --global user.email / user.name` was unset. **Things skipped:** `make fmt` and `make codequality` fail because `keep-sorted` and `license-lint`…
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 25 minutes.
- Recovered from all 4 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.
- 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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.12 | |
| Argusic Runner | 1/3 | Runs with mocks | 87.00 | 0.10 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/gopass)Questions
- Does gopass run?
- Yes. gopass runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test gopass?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e2dd748cdbe1. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test gopass?
- The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does gopass take to install?
- 25 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 gopass need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing gopass?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for gopass?
- 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.