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 16 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
gopass builds from source, all 50 unit test packages pass, and the binary runs end-to-end with the age backend (setup, insert, show, list all succeed).
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 95.7 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 binary not found (no root for apt install)4 minutes
- Go >=1.25 not in system repos (apt has 1.22-1.24)3 minutes
- gpg-agent multi-call binary misidentified by argv[0], causing 'invalid option --yes' test failures2 minutes
- pinentry-curses needs a real TTY and fails with 'isatty' error2 minutes
- age setup generates a random passphrase that the pinentry wrapper doesn't know1 minute
- Install time
- 16 minutes
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- make test exited 0 (50/50 packages OK); ./gopass --version returned 'gopass 1.17.0-git+db760006 (1e939616) go1.26.8 linux amd64'; end-to-end: setup --crypto age --storage fs creates store, insert/show/list round-trips correctly
- Model tokens used
- 240,896
- 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
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 3, run , 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.
Now I have all the data. Here's my summary: **What happened:** - Built `gopass` from source (Go 1.26.8 downloaded since not in apt repos) - All 50 unit test packages passed - Verified end-to-end: `gopass setup --crypto age --storage fs` created a store, `gopass insert` wr… tokens used 240,896 Now I have all the data. Here's my summary: **What happened:** - Built `gopass` from source (Go 1.26.8 downloaded since not in apt repos) - All 50 unit test packages passed - Verified end-to-end: `gopass setup --crypto age --storage fs` created a store, `gopass insert` wr…
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 5 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 3 times, so the result is not a one-off.
What did not, or is not known
- Took 16 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
Of the 4 git projects Argusic has installed and timed, gopass was the 3rd fastest to reach a running state, and 4 of 4 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
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 16 minutes, hitting 5 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. 3 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?
- 16 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?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does gopass compare with the alternatives?
- Of the 4 git projects Argusic has installed and timed, gopass was the 3rd fastest to reach a running state, and 4 of 4 reached one at all.
- Where is the evidence for gopass?
- All 3 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.