app-tailscale

Tailscale - Home Assistant Community App

Could not verifysource: GitHubShellMITcommit 2f295975bcd5

Shell, MIT licensed. The project labels itself: addon, addons, app, apps, hassio, home assistant, homeassistant and tailscale.

Argusic could not get app-tailscale running. An Argusic agent installed it in 7.2 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All 131 bash scripts pass syntax check, 3 YAML files parse correctly, Dockerfile is structurally complete, s6 overlay hierarchy consistent, config schema matches translations, repo is clean with no modifications needed but cannot be built or launched in this non-root, no-Docker, user-namespace-disabled 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 10 of 100 (the mean of this project's run scores).

At a glance

verdict
Could not verify
Argusic Score
10 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
2
last tested
stars
572
forks
135
open issues
10
watchers
7
size
1 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 app-tailscale, 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.

  • Docker daemon unavailable (user namespaces disabled, no root)5 minutes
  • Cannot build Docker image without running Docker daemon2 minutes
Install time
7 minutes
Cold machine to finish
9 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
not verified, cannot build or run without Docker daemon and HA supervisor environment
Model tokens used
328,407
Exact commit tested
2f295975bcd5
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.

2. **Static analysis** (all passed):
   - All 3 YAML files valid (config.yaml, build.yaml, translations)
   - All 131 shell scripts pass `bash -n` syntax check
   - Dockerfile structurally valid (FROM, RUN, COPY rootfs, HEALTHCHECK, s6 stage2 hook)
   - 22 s6 services defined (10 longrun + 11 oneshot + 1 bundle)
   - Config schema (19 entries) consistent with options (18 defaults)
   - Translatio`ns match config (exit_node is an optional parameter with no default — expected)
   - nginx config, templates, and mime.types all present
   - AppArmor profile present
3. **Could not build/launch**: This is a Home Assistant supervisor addon. Building requires Docker …
4. **What mocking would need**: A full Home Assistant supervisor mock (bashio library, supervisor A…
5. **No changes needed**: The repo is clean (`git status` shows nothing to commit, working tree cle…

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 2 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

  • An agent with no time limit did not get it running.
  • Took 7.2 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.

Of the 4 addon projects Argusic has installed and timed, app-tailscale was the 3rd fastest to reach a running state, and 2 of 4 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/3Did not run20.000.03
Argusic Runner1/3Did not run0.000.02

Topics (from GitHub)

addonaddonsappappshassiohome-assistanthomeassistanttailscalevpnwireguard

Embed the badge

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

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

Questions

Does app-tailscale run?
Argusic could not verify that app-tailscale runs. Argusic installed and launched it on a clean machine in 7 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test app-tailscale?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2f295975bcd5. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test app-tailscale?
The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does app-tailscale take to install?
7.2 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 app-tailscale need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing app-tailscale?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does app-tailscale compare with the alternatives?
Of the 4 addon projects Argusic has installed and timed, app-tailscale was the 3rd fastest to reach a running state, and 2 of 4 reached one at all.
Where is the evidence for app-tailscale?
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