wireguard-install
WireGuard VPN installer for Linux servers
Could not verifysource: GitHubhomepageShellMITcommit 832fb9833501
Shell, MIT licensed. The project labels itself: linux, nat, privacy, vpn and wireguard.
Argusic could not get wireguard-install running. An Argusic agent installed it in 0 minutes and hit 1 error on a clean machine with no GPU, and the whole session was recorded.
Script passes syntax validation and linting; all internal functions verified in mock environment; real execution blocked by missing root privilege, wireguard kernel module, and systemd in container
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 25 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.
- Cannot run script directly: requires root, wireguard kernel module, and systemd, none of which are available in container
- Install time
- under a minute
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 1 hit, 0 fixed with no human help
- How the result was proved
- bash -n (syntax ok), shellcheck (0 warnings, CI-identical excludes), shfmt (no diff), mock environment validated all 22 functions, variable assignment, key generation, config templates, and getHomeDirForClient logic
- Model tokens used
- 123,518
- Exact commit tested
- 832fb9833501
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
123,518 All tests done. Here's the summary: **Install**: No dependencies to install — the repo is a single bash script. Syntax check (`bash -n`… **Testing approach**: Since the script requires root, a real WireGuard kernel module, and systemd —… - All 22 functions load correctly - `checkOS` correctly identifies Ubuntu 24.04 - `installQuestions` auto-answers all prompts and sets variables (`SERVER_PUB_IP`, `SERVER_PUB_NIC`… - Key generation via mocked `wg genkey/pubkey/genpsk` produces valid-format outputs - Server and client WireGuard config templates render correctly with all fields populated - `getHomeDirForClient` returns correct paths in all three scenarios (no user/SUDO_USER, SUDO_USER=… - `manageMenu`, `newClient`, `listClients`, `revokeClient`, `uninstallWg` all defined and callable **Root cause of no real run**: The container lacks root privileges, the WireGuard kernel module, an…
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
- Installed in 0 minutes.
- 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
- An agent with no time limit did not get it running.
- Hit 1 error during setup, 1 of which were not solved.
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 | Did not run | 20.00 | 0.02 | |
| Argusic Runner | 1/3 | Did not run | 30.00 | 0.02 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/wireguard-install)Questions
- Does wireguard-install run?
- Argusic could not verify that wireguard-install runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test wireguard-install?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 832fb9833501. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test wireguard-install?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does wireguard-install take to install?
- 0 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 wireguard-install need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing wireguard-install?
- 1 thing broke in the recorded run. Each one, and the time it cost, is listed on this page.
- Where is the evidence for wireguard-install?
- 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.