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 25 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

NiubiGEO v0.2.1 builds cleanly, all 256 unit tests pass with 10 intentional skips, all 17 example tests pass, product server starts and responds 200 on /health and /

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

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.07 (measured)
recorded runs
1
last tested
stars
4,866
forks
309
open issues
12
watchers
102
size
33 MB
created
last push

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.

Time lost to each failure while testing niubigeo, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Node 22.0.0 has globalThis.fetch as a getter; t.mock.method(globalThis, 'fetch') throws TypeError8 minutes
  • Container has Node 18 but project requires Node >=225 minutes
  • Leftover node_modules_old directory was scanned by the regex constraint test, causing 1 false failure2 minutes
Install time
25 minutes
Cold machine to finish
13 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
npm run self-check exited 0: 256 passed, 0 failed, 10 skipped; npm run test:examples exited 0: 17 passed, 0 failed; product server started and responded 200 on /health and 200 on /
Model tokens used
125,935
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.

**No mock server needed**: the unit test suite uses `t.mock.method(globalThis, 'fetch', ...)` to mo…
tokens used
125,935
This project is **NiubiGEO v0.2.1** — an open-source AI brand-visibility tracker (TypeScript, Node.…
- **Install**: `npm install` + `npm run build` (tsc compiles `src/` to `dist/`).
- **Tests**: Two suites — `npm run self-check` (256 pass, 0 fail, 10 skipped) and `npm run test:exa…
- **Server**: `npm run server` starts the product server on port 8787 (configurable via `PORT`). Bo…
**3 errors fixed**:
1. Node 18 in the container vs. project requirement of ≥22 — downloaded Node 22.12.0 and used it vi…
2. Node 22.0.0 has `globalThis.fetch` as a getter, so `t.mock.method(globalThis, 'fetch')` crashed …
3. A stale `node_modules_old/` directory made the regex-constraint test scan third-party code — rem…
**No mock server needed**: the unit test suite uses `t.mock.method(globalThis, 'fetch', ...)` to mo…

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 3 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.

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 25 minutes to install, slower than the median of the 20 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 21 TypeScript projects Argusic has installed and timed, niubigeo was the 21st fastest to reach a running state, and 17 of 21 reached one at all.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.07

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/niubigeo.svg)](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 25 minutes, hitting 3 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. One attempt is 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.07: 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?
25 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?
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.
How does niubigeo compare with the alternatives?
Of the 21 TypeScript projects Argusic has installed and timed, niubigeo was the 21st fastest to reach a running state, and 17 of 21 reached one at all.
Where is the evidence for niubigeo?
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.

Discussion