Does domainstack.io run?

Yes. domainstack.io 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 domainstack.io?

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

What did it cost to test domainstack.io?

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

How long does domainstack.io take to install?

6.5 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 domainstack.io need a GPU?

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

What goes wrong when installing domainstack.io?

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 domainstack.io?

All 4 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.

domainstack.io

🧰 All-in-one domain name intelligence as a service

Runssource: GitHub homepageTypeScriptMITcommit 88b8831009b8

TypeScript, MIT licensed. The project labels itself: ai sdk, better auth, dns, domains, hacktoberfest, mcp, nextjs and polar.

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

pnpm install completed with all dependencies, pnpm build produces a complete .next build output, the dev server starts and responds 200 on / and /api/healthz, all 527 tests pass through turbo (66 test files, 0 failures), oxlint reports 0 warnings/errors across all 18 packages, and oxfmt confirms all files use correct format.
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 93.3 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 93.3 / 100
cost of the verifying run: $0.13 (measured)
recorded runs: 4
last tested: 2026-09-09
stars: 291
forks: 21
open issues: 10
watchers: 4
size: 11 MB
created: 2025-09-13
last push: 2026-09-22

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

System Node.js is v18.19.1 but project requires >=242.3 minutes
Web app browser tests required Playwright/Chromium but browsers were not installed2.1 minutes
Puppeteer postinstall failed - no unzip binary to extract Chrome0.7 minutes
Build failed: auth module requires at least one OAuth provider configured at build time0.5 minutes

Install time: 7 minutes
Cold machine to finish: 28 minutes
Errors hit and fixed: 4 hit, 4 fixed with no human help
How the result was proved: pnpm run test: 66 test files passed, 527 tests passed (0 failures). pnpm run lint: 18/18 successful, 0 warnings/errors. pnpm run fmt:check: 18/18 successful. next build: compiled all routes successfully. Next.js dev server started and responded on /api/healthz with 200 and / with 200.
Model tokens used: 140,335
Exact commit tested: 88b8831009b8
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

The end of the recording

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

trace
trace-build
turbopack
types
workflow-data
Build output exists
Everything is verified. Let me compile the final result:
ARUGIC_RESULT: {"install_succeeded":true,"launch_succeeded":true,"install_minutes":6.5,"errors":[{"…
tokens used
140,335
Everything is verified. Let me compile the final result:
ARUGIC_RESULT: {"install_succeeded":true,"launch_succeeded":true,"install_minutes":6.5,"errors":[{"…

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 6.5 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 MIT, as reported by its host.
Measured 4 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 6.5 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	3/3	Ran out of time	0.00	0.26	2026-09-09 02:55 UTC
Argusic Runner	1/3	Ran out of time	0.00	0.18	2026-09-08 23:34 UTC
Argusic Runner	2/3	Runs	86.67	0.06	2026-09-08 22:21 UTC
Argusic Runner	1/3	Runs	100.00	0.13	2026-09-08 20:22 UTC

Topics (from GitHub)

ai-sdk better-auth dns domains hacktoberfest mcp nextjs polar rdap security tailwindcss typescript vercel whois workflow-sdk

Embed the badge

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

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

Questions

Does domainstack.io run?: Yes. domainstack.io 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 domainstack.io?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 88b8831009b8. 4 attempts are recorded, and the full method is on the methodology page.
What did it cost to test domainstack.io?: The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does domainstack.io take to install?: 6.5 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 domainstack.io need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing domainstack.io?: 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 domainstack.io?: All 4 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.