niubigeo
Open-source AI brand visibility and competitor reports. Official website: https://niubigeo.ai/ | Paid services: AI testing by real people and GEO optimization. Pricing: https://niubigeo.ai/pricing
Runs with mockssource: GitHubhomepageTypeScriptApache-2.0commit 8bc65e9d9093
TypeScript, Apache-2.0 licensed.
niubigeo runs, with stand-ins for the services it depends on. An Argusic agent installed it in 10 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Build compiles all TypeScript, the server answers HTTP 200 at port 8787 with NiubiGEO UI, and the full test suite passes (256 pass, 0 fail, 10 skip)
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 92 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.
- 4 tests failed with TypeError: The argument 'methodName' must be a method7 minutes
- Node.js 18 installed but project requires >=223 minutes
- Install time
- 10 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- npm run self-check exited 0, 256 passed 0 failed 10 skipped; curl localhost:8787 returned HTTP 200
- Model tokens used
- 113,025
- Exact commit tested
- 8bc65e9d9093
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
113,025
All verified. Now let me compile the final result.
**Summary of what I did:**
1. **Node.js version mismatch**: The project requires Node >=22 but the container had Node 18. I do…
2. **Install and build**: Ran `npm install` (39 packages added) and `npm run build` (tsc compiled s…
3. **Test failures diagnosed**: 4 tests failed with `"The argument 'methodName' must be a method. R…
4. **Fix applied to 3 test source files** (`test/structured-provider-retry.test.ts`, `test/product-…
- `const _orig_fetch = globalThis.fetch; t.after(() => { globalThis.fetch = _orig_fetch; }); glo…
5. **Full test suite**: 256 pass, 0 fail, 10 skipped.
6. **Server**: Already running (on port 8787), returns HTTP 200.
7. **CLI**: `npm run projects` and `npm run audit --help` both work.
Here's the final ARGUSIC_RESULT: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
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 10 minutes to install, slower than the median of the 35 comparable projects Argusic has measured.
Of the 36 TypeScript projects Argusic has installed and timed, niubigeo was the 32nd fastest to reach a running state, and 30 of 36 reached one at all.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.27 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.07 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/niubigeo)Questions
- Does niubigeo run?
- niubigeo runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 10 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test niubigeo?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8bc65e9d9093. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test niubigeo?
- The run that produced this verdict cost $0.27: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does niubigeo take to install?
- 10 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 niubigeo need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing niubigeo?
- 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.
- How does niubigeo compare with the alternatives?
- Of the 36 TypeScript projects Argusic has installed and timed, niubigeo was the 32nd fastest to reach a running state, and 30 of 36 reached one at all.
- Where is the evidence for niubigeo?
- 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.