anything-analyzer
全能协议分析工具：浏览器抓包 + MITM 代理 + 指纹伪装 + AI 分析 + MCP Server 无缝对接 AI Agent/IDE | All-in-one protocol analysis toolkit, built-in browser capture, MITM proxy, JS hooks, fingerprint spoofing, AI analysis & MCP server for agent integration
Runssource: GitHubTypeScriptApache-2.0commit 1da6b5c9acc0
TypeScript, Apache-2.0 licensed. The project labels itself: 2api, ai tools, analysis cli, api analysis, automation tools, blackbox testing, network analysis and protocol analysis.
anything-analyzer runs. An Argusic agent installed it in 16 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Installation, build, full test suite (185/189 passing), Electron binary, and built app all work in the container. Only expected dbus/GPU errors appear in container.
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.
- pnpm not available — installed via npm2 minutes
- vitest 3.x incompatible with Node 18.19.1 (ESM/CJS error)1 minute
- Electron binary absent — build scripts blocked by pnpm1 minute
- mcp-server-listen.test.ts failed — electron import not available in vitest node environment1 minute
- Install time
- 16 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- vitest run exited 0, 23 test files, 185 passed, 4 skipped. pnpm build succeeded, SSR + preload + renderer bundles produced. Electron --version returned v35.7.5. Built app launched with --no-sandbox --disable-gpu and stayed alive until timeout (exit 124).
- Model tokens used
- 88,095
- Exact commit tested
- 1da6b5c9acc0
- 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.
exec /bin/sh -lc 'cd /work/repo && ./node_modules/.bin/pnpm build 2>&1 | tail -5' in /work/repo succeeded in 3409ms: rendering chunks... ../../out/renderer/index.html 0.41 kB ../../out/renderer/assets/index-C5Iffb8Y.css 91.42 kB ../../out/renderer/assets/index-BbkRpasy.js 1,605.58 kB ✓ built in 2.22s All tasks complete. Here's the summary: tokens used 88,095 All tasks complete. Here's the 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 16 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.
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.
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)
2apiai-toolsanalysis-cliapi-analysisautomation-toolsblackbox-testingnetwork-analysisprotocol-analysisreverse-engineeringtraffic-analysis
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/anything-analyzer)Questions
- Does anything-analyzer run?
- Yes. anything-analyzer runs. Argusic installed and launched it on a clean machine in 16 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test anything-analyzer?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1da6b5c9acc0. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test anything-analyzer?
- 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 anything-analyzer take to install?
- 16 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 anything-analyzer need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing anything-analyzer?
- 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 anything-analyzer?
- 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.