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

How did Argusic test Purse?

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

What did it cost to test Purse?

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

How long does Purse take to install?

10 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 Purse need a GPU?

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

What goes wrong when installing Purse?

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.

Where is the evidence for Purse?

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.

Purse

Manage secrets with Bash and GnuPG asymmetric encryption (YubiKey)

Runssource: GitHub homepageShellMITcommit 9b2f643cdd21

Shell, MIT licensed. The project labels itself: bash, bash script, cryptography, encryption, file encryption, gnupg, gpg and password.

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

Purse password manager runs with gpg extracted from debs, RSA 2048 encryption subkey, writes/reads/lists passwords and creates backup archives; read falsely reported 'Failed to decrypt' before the emit_pass clear-exit-code fix.
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.09 (measured)
recorded runs: 1
last tested: 2026-09-09
stars: 615
forks: 43
open issues: 0
watchers: 14
size: 0 MB
created: 2018-06-02
last push: 2026-07-26

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

gpg binary not installed in container4 minutes
gpg-agent binary not found at hardcoded /usr/bin/gpg-agent path2 minutes
setup_keygroup() grep for 'sec#' does not match non-smartcard keys (shows empty recommended IDs)2 minutes
GPG key had no encryption subkey (only SC - Sign/Certify)1 minute
clear command returns exit code 1 in non-TTY environment, causing emit_pass to fail incorrectly1 minute

Install time: 10 minutes
Cold machine to finish: 15 minutes
Errors hit and fixed: 5 hit, 5 fixed with no human help
How the result was proved: ./purse.sh w finalTest 14 wrote password; ./purse.sh r finalTest printed password; ./purse.sh l listed entries; ./purse.sh b created valid tar backup; manual gpg --decrypt of .asc safe files confirmed all passwords decrypt correctly
Model tokens used: 163,357
Exact commit tested: 9b2f643cdd21
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.

# Actually, let me compute the time spent
echo "Time check: starting from scratch"
echo "Starting time estimate: 11:54 (init)"
echo "Current time: $(date)"' in /work/repo
 succeeded in 0ms:
Time check: starting from scratch
Starting time estimate: 11:54 (init)
Current time: Wed Sep  9 12:09:14 UTC 2026
About 15 minutes total. Here's my final assessment:
tokens used
163,357
About 15 minutes total. Here's my final assessment:

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.

What did not, or is not known

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

Of the 5 bash projects Argusic has installed and timed, Purse was the 4th fastest to reach a running state, and 4 of 5 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.
A quick evaluation: it was running 10 minutes after the clone.

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.09	2026-09-09 12:09 UTC

Topics (from GitHub)

bash bash-script cryptography encryption file-encryption gnupg gpg password password-manager secrets secrets-management security unix

Embed the badge

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

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

Questions

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