Yes. shynet runs. Argusic installed and launched it on a clean machine in 7 minutes, hitting 4 errors on the way, and recorded the session.

How did Argusic test shynet?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit ca35caba3af2. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test shynet?

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

How long does shynet take to install?

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

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

What goes wrong when installing shynet?

4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for shynet?

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.

shynet

Modern, privacy-friendly, and detailed web analytics that works without cookies or JS.

Runssource: GitHubPythonApache-2.0commit ca35caba3af2

Python, Apache-2.0 licensed. The project labels itself: a17t, analytics, django, docker, kubernetes, monitoring, noscript and privacy.

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

Shynet 0.13.1 is installed with SQLite backend, all 11 tests pass (9 API + 2 dashboard), Django admin user creation works via registeradmin, and Gunicorn serves the health check endpoint at 200 and login page at 200.
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.04 (measured)
recorded runs: 2
last tested: 2026-09-17
stars: 3,155
forks: 209
open issues: 64
watchers: 30
size: 35 MB
created: 2020-04-09
last push: 2026-03-15

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

poetry install failed building frozenlist 1.3.1 and multidict 6.0.2 from source (missing python3-dev headers)2 minutes
django-health-check v4 removed health_check.db and health_check.cache submodules that Shynet INSTALLED_APPS requires1 minute
allauth.account.middleware.AccountMiddleware not in MIDDLEWARE (required by django-allauth 65.x)1 minute
collectstatic failed because NPM_ROOT_PATH='../' resolved to /work instead of /work/repo1 minute

Install time: 7 minutes
Cold machine to finish: 6 minutes
Errors hit and fixed: 4 hit, 4 fixed with no human help
How the result was proved: DJANGO_SETTINGS_MODULE=shynet.settings python -m pytest shynet/ -v exited 0, 11 passed; gunicorn serving /healthz/ returned 200 HTML with Cache OK and DatabaseBackend OK
Model tokens used: 124,366
Exact commit tested: ca35caba3af2
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

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 1, run 2026-09-03. The verdict above comes from a different attempt, so read this as one session and not as the current result. 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.

System check identified some issues:
WARNINGS:
?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: settings.ACCOUNT_LOGIN_METHODS = {'em…
?: settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*', …
?: settings.ACCOUNT_USERNAME_REQUIRED is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*…
Successfully created a Shynet superuser
Email address: [email protected]
Password: qSJIHgtWDQ
Here is my full report:
tokens used
124,366
Here is my full 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

Reached a running state on a clean machine, with the session recorded.
Installed in 7 minutes.
Recovered from all 4 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 Apache-2.0, as reported by its host.
Measured 2 times, so the result is not a one-off.

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 7 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	2/3	Runs	100.00	0.04	2026-09-17 19:22 UTC
Argusic Runner	1/3	Runs	100.00	0.16	2026-09-03 09:10 UTC

Topics (from GitHub)

a17t analytics django docker kubernetes monitoring noscript privacy python security self-hosted web-analytics

Embed the badge

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

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

Questions

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