super

One wifi password per device. Ad Blocking & Privacy Blocklists. Policy Based Network Access

Runs with mockssource: GitHubhomepageJavaScriptBSD-3-Clausecommit 0010d454a60a

JavaScript, BSD-3-Clause licensed. The project labels itself: adblock, agent isolation, alerting, coredns, golang, homelab, internet filtering and kvm server.

super runs, with stand-ins for the services it depends on. An Argusic agent installed it in 12 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.

Go API builds and 69 unit tests pass covering DNS, validation, alerts, parental controls, scheduling, forwarding rules, and plugin networking.

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

At a glance

verdict
Runs with mocks
Argusic Score
52.7 / 100
cost of the verifying run
$0.11 (measured)
recorded runs
2
last tested
stars
905
forks
68
open issues
31
watchers
4
size
36 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 super, 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.

  • Go binary not found in container; installed go1.26.6 manually from golang.org3 minutes
  • Missing /test/configs and state directories for API test environment2 minutes
  • 31 nftables/netlink tests fail with 'operation not permitted' and 1 fails with 'nft: not found' and 1 with 'ip: not found' — all require root/net_admin privileges
Install time
12 minutes
Cold machine to finish
12 minutes
Errors hit and fixed
3 hit, 2 fixed with no human help
How the result was proved
go test -v -count=1 ./... in api/code/: 69 PASS, 32 FAIL; all failures from nftables/netlink permission errors
Model tokens used
342,851
Exact commit tested
0010d454a60a
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

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- **Frontend (`frontend/`)**: React Native app with native dependencies — can't build in this conta…
- **Test runner (`tests/runner/code/`)**: Node.js deps installed. Tests require a running SPR API e…
**Errors encountered:**
1. Go not installed → downloaded Go 1.26.6 binary
2. Missing test config directories → created and populated from template configs
3. nftables/netlink operations fail → requires root (expected, not fixable)
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 1…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 12, "errors": [{"msg": "Go…
tokens used
342,851

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 12 minutes.
  • Licensed BSD-3-Clause, 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.
  • Hit 3 errors 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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks85.330.11
Argusic Runner1/3Did not run20.000.16

Topics (from GitHub)

adblockagent-isolationalertingcorednsgolanghomelabinternet-filteringkvm-servernftablesparental-controlroutersecuritysecurity-toolsself-hostedvpnwifiwifi-securitywireguard

Embed the badge

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

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

Questions

Does super run?
super runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 12 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test super?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0010d454a60a. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test super?
The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does super take to install?
12 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 super need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing super?
3 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.
Where is the evidence for super?
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