analog
The fullstack meta-framework for Angular. Powered by Vite and Nitro
Runssource: GitHubhomepageTypeScriptMITcommit 0a15065658e7
TypeScript, MIT licensed. The project labels itself: angular, framework, fullstack, meta framework, nitro, router, server side rendering and ssg.
analog runs. An Argusic agent installed it in 1 minute and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 21 projects build successfully, all 19 project test suites pass, and the streaming-app server binary starts and serves on the configured port.
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.
- Build failed: native bindings not found for 7 apps (installed under Node 18, running on Node 22)5 minutes
- Node.js v18 too old (required ^22.22.3 || ^24.15.0)2 minutes
- Test failures: Playwright browser not installed2 minutes
- Test failures in platform:typed-routes-consumer spec timed out at 5s default2 minutes
- pnpm not pre-installed (required pnpm v11+)1 minute
- Install time
- 1 minutes
- Cold machine to finish
- 85 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- pnpm test exited 0, all 19 project test suites passed; pnpm build exited 0, all 21 projects built; server binary started and listened on port 3199
- Model tokens used
- 192,538
- Exact commit tested
- 0a15065658e7
- 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.
The server starts (port 3000 already used from previous test, but the binary is functional). Let me… exec /bin/sh -lc 'cd /work/repo && export PATH="/home/runner/.local/node/node-v22.22.3-linux-x64/bin:$PA… succeeded in 7857ms: Listening on http://[::]:3199 EXIT: 124 The server starts and listens on port 3199. Exit code 124 means `timeout` killed it after 8 seconds… Now let me compile the final summary: tokens used 192,538 The server starts and listens on port 3199. Exit code 124 means `timeout` killed it after 8 seconds… Now let me compile the final summary:
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 1 minute.
- Recovered from all 5 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 1 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
Topics (from GitHub)
angularframeworkfullstackmeta-frameworknitrorouterserver-side-renderingssgssrstatic-site-generatorviteweb
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/analog)Questions
- Does analog run?
- Yes. analog runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test analog?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0a15065658e7. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test analog?
- The run that produced this verdict cost $0.25: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does analog take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does analog need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing analog?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for analog?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.