VengeanceUI
VengeanceUI helps you to build your landing page by providing you animated beautiful components out of the box which you can copy and paste and make your landing page Awesome ,Subtle and of course Tasteful.
Runssource: GitHubhomepageTypeScriptMITcommit 813d9c192b1f
TypeScript, MIT licensed.
VengeanceUI runs. An Argusic agent installed it in 2 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The VengeanceUI Next.js application builds and serves 101 pages including homepage, components, docs, and API endpoints over HTTP.
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
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.
- Node.js 18.19.1 is too old for Next.js 16 (requires >=20.9.0)1 minute
- npm install with Node 18 produced broken @tailwindcss/oxide native binding on x64 linux1 minute
- Build process ran out of memory (heap OOM)0.3 minutes
- Install time
- 2 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npm run build exited 0, 101 pages compiled. next start on port 3462 returned: homepage 200 (399951B), /components 200 (253958B), /docs/install-nextjs 200 (108632B), /api/github-stars 200 (valid JSON)
- Model tokens used
- 39,892
- Exact commit tested
- 813d9c192b1f
- 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.
No test suite was present to run (the package.json has no test script). This is a UI component webs… 2026-09-08T21:55:07.219587Z ERROR codex_core::session: failed to record rollout items: thread 01a08… tokens used 39,892 The build is complete and the app serves pages. Let me compile the final ARGUSIC_RESULT. **Summary of what happened:** 1. **Node version issue**: The container has Node 18.19.1 but Next.js 16 requires >=20.9.0. Fix: do… 2. **npm install with Node 18 installed wrong optional deps**: `@tailwindcss/oxide` native binding … 3. **Out-of-memory during TypeScript check**: The initial build ran out of heap on Node 20's defaul… 4. The build completed successfully: 101 pages (static + SSG + 1 dynamic route). 5. The app starts and serves content: homepage returns 200 with ~400KB HTML, components page return… No test suite was present to run (the package.json has no test script). This is a UI component webs…
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 2 minutes.
- Recovered from all 3 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 2 minutes after the clone.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/vengeanceui)Questions
- Does VengeanceUI run?
- Yes. VengeanceUI runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test VengeanceUI?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 813d9c192b1f. 4 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test VengeanceUI?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does VengeanceUI take to install?
- 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 VengeanceUI need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing VengeanceUI?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for VengeanceUI?
- 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.