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 7 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Project installs, builds, and all 23 test suites pass (185 tests) with electron-vite build completing successfully and electron binary reporting v35.7.5
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.
- Electron binary not downloaded due to postinstall script being ignored4 minutes
- ESM-only vite 7 not loadable by Node 18 via vitest's CJS config loader2 minutes
- Install time
- 7 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- pnpm test: all 23 test files passed, 185 tests passed, 4 skipped; electron --version returns v35.7.5; electron-vite build completes successfully
- Model tokens used
- 123,928
- 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.
The Electron app can't fully start because there's no GPU in this environment. This is a container … Let me check the `too many open files` error: exec /bin/sh -lc 'ulimit -n 2>&1' in /work/repo succeeded in 0ms: 524288 That's fine - it's just during concurrent starts from multiple electron processes during testing. N… Now let me finalize the report: tokens used 123,928 That's fine - it's just during concurrent starts from multiple electron processes during testing. N… Now let me finalize the report:
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 7 minutes.
- Recovered from all 2 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.
- 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 7 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)
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 7 minutes, hitting 2 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. 2 attempts are 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.06: 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?
- 7 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?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for anything-analyzer?
- 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.