lazywarden

Automatic Bitwarden Backup

Runs with mockssource: GitHubhomepagePythonMITcommit 85afd87a3b26

Python, MIT licensed. The project labels itself: backup, bitwarden, encryption, server and vaultwarden.

lazywarden runs, with stand-ins for the services it depends on. An Argusic agent installed it in 10 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The Lazywarden Bitwarden backup application installs, imports all modules, and completes its full backup pipeline: environment loading, Bitwarden SDK initialization via mock, secret retrieval, vault operations via mock CLI, AES-256 encryption with Argon2 KDF, encrypted ZIP creation, and SHA-256 hash verification, producing valid encrypted backup archives at /home/runner/lazywarden/backup-drive/

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 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.12 (measured)
recorded runs
2
last tested
stars
836
forks
25
open issues
31
watchers
8
size
0 MB
created
last push

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.

Time lost to each failure while testing lazywarden, 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.

  • pycrypto package fails to build from source (needs python3-dev headers which require root to install)3 minutes
  • Bitwarden SDK native module requires real Bitwarden server credentials3 minutes
  • bitwarden_client.py has hardcoded /root/.config/Bitwarden CLI path, fails with PermissionError1 minute
  • backup.py and import_to_bitwarden.py use hardcoded /usr/local/bin/bw path1 minute
  • .env missing required vars (ACCESS_TOKEN, ORGANIZATION_ID, BACKUP_DIR) and has /root/ paths1 minute
  • bw CLI not found (not installed), Bitwarden CLI required for subprocess calls1 minute
Install time
10 minutes
Cold machine to finish
9 minutes
Errors hit and fixed
6 hit, 6 fixed with no human help
How the result was proved
Ran main() via python3 with mocked SDK and bw CLI, observed 'Bitwarden backup completed successfully' log output and verified valid AES-encrypted ZIP archives (with pyzipper.AESZipFile) in /home/runner/lazywarden/backup-drive/ containing encrypted JSON and attachments ZIP
Model tokens used
128,504
Exact commit tested
85afd87a3b26
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
Behaviour against real services
this run was verified against stand-in services only

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

/home/runner/lazywarden/backup-drive/bw-backup_2026_11_21_22_24_29.zip
/home/runner/lazywarden/backup-drive/bw-backup_2026_11_21_22_24_33.zip
/home/runner/lazywarden/backup-drive/bw-backup_2026_11_21_22_25_08.zip
Latest backup: bw-backup_2026_11_21_22_25_08.zip
Contents: ['bw-backup_2026_11_21_22_25_08.json', 'attachments_2026_11_21_22_25_08.zip']
  bw-backup_2026_11_21_22_25_08.json: 212 bytes
  attachments_2026_11_21_22_25_08.zip: 190 bytes
ZIP verification: PASSED
Everything is verified. Here is the final report:
tokens used
128,504
Everything is verified. Here is the final report:

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

  • Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
  • 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

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 10 minutes to install, slower than the median of the 47 comparable projects Argusic has measured.

Of the 48 backup projects Argusic has installed and timed, lazywarden was the 38th fastest to reach a running state, and 32 of 48 reached one at all.

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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks92.000.12
Argusic Runner1/3Runs with mocks92.000.84

Topics (from GitHub)

backupbitwardenencryptionservervaultwarden

Embed the badge

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

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

Questions

Does lazywarden run?
lazywarden runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 10 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test lazywarden?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 85afd87a3b26. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test lazywarden?
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 lazywarden 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 lazywarden need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing lazywarden?
6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does lazywarden compare with the alternatives?
Of the 48 backup projects Argusic has installed and timed, lazywarden was the 38th fastest to reach a running state, and 32 of 48 reached one at all.
Where is the evidence for lazywarden?
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.

Discussion