evlog
Digging through logs is not observability. It's hope, wide events, structured errors, TypeScript-first, every runtime.
Runssource: GitHubhomepageTypeScriptMITcommit cced5e896135
TypeScript, MIT licensed. The project labels itself: debugging, error handling, logger, logging, nextjs, nuxt, observability and otlp.
evlog runs. An Argusic agent installed it in 6 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 35 workspace packages install and build on Node 24. Test suite passes (1905/1907 tests, 90/91 files), lint and typecheck clean. CLI binary outputs help text. Package dist exposes 35 named exports via ESM.
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 v18.19.1 too old; requires v24.21.0. Packages (tsdown, @clack/core, Nuxt CLI) use node:util.styleText which doesn't exist in v18.1 minute
- pnpm not found in PATH and corepack missing.1 minute
- npm install -g failed with EACCES on /usr/local/lib
- Install time
- 6 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pnpm run test exited 0: 90 test files passed, 1905 tests passed, 2 skipped. Also verified CLI help output and package ESM imports.
- Model tokens used
- 56,608
- Exact commit tested
- cced5e896135
- 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.
**Errors encountered:** 1. **Node.js version too old (v18.19.1, needs v24)** — `pnpm install` succeeded with warnings, but … 2. **`pnpm` not found in PATH** — corepack not available, installed pnpm globally via npm to `$HOME… 3. **`npm install -g pnpm` failed with EACCES** — `/usr/local/lib` not writable. Fixed by using `--… **Verification:** - `pnpm install` — succeeded, 2688 packages installed - `pnpm run dev:prepare` — 13 tasks successful, generated types and built all packages - `pnpm run test` — 90 passed, 1 skipped, 1905 tests passed, 2 skipped - `pnpm run lint` — 22 tasks successful, no lint errors - `pnpm run typecheck` — 27 tasks successful, no type errors - `node packages/cli/bin/evlog.mjs --help` — printed CLI help for evlog v0.6.3 - `import * as mod from './packages/evlog/dist/index.mjs'` — verified 35 named exports are present
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 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 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 6 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)
debuggingerror-handlingloggerloggingnextjsnuxtobservabilityotlpposthogsentrytypescriptwide-events
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/evlog)Questions
- Does evlog run?
- Yes. evlog runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test evlog?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit cced5e896135. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test evlog?
- 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 evlog take to install?
- 6 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 evlog need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing evlog?
- 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 evlog?
- 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.