indie-wiki-buddy
Browser extension that automatically notifies and redirects you to independent wikis.
Could not verifysource: GitHubhomepageJavaScriptMITcommit b11d029ff0aa
JavaScript, MIT licensed. The project labels itself: extension, hacktoberfest and wiki.
Argusic could not get indie-wiki-buddy running. An Argusic agent installed it in 0 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The repository is a browser extension with valid Chrome and Firefox manifests, 846 wiki redirect entries, 33 locale translations, 941 files in the distributable zip, and core JavaScript modules that parse correctly and pass all unit tests.
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 35 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.
- Install time
- under a minute
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- web-ext@9 build exits 0 producing a valid zip; 17/17 unit tests pass covering loadSiteData, getSiteDataByOrigin, findMatchingSite, isSearchEngineOn, isValidHostname, encodeArticleTitle, safeDecodeURI, getNewURL, getOriginArticle, and data integrity checks
- Model tokens used
- 84,495
- Exact commit tested
- b11d029ff0aa
- 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.
**Repository overview:** Indie Wiki Buddy v4.0.1 — a browser extension (no build tooling, no packag…
**What I verified:**
1. All 43 JS files pass syntax check via `node --check`
2. All 33 locale files are valid JSON
3. `data.json` (846 wiki sites) is valid JSON with clean structure
4. `web-ext` builds both Chrome and Firefox variants into valid zip archives (941 files each)
5. Core module (`scripts/common-functions.js`) can be imported in Node.js with a mocked browser API…
**Limitations encountered:**
- No browser (Chrome/Firefox) is available in the container, so the extension cannot be literally "…
- `web-ext lint` fails on the current version (v10) due to Node.js 18 compatibility in `undici`; `w…
- No test suite existed in the repo; no formal install process exists beyond the browser's extensio…
- The `package.json` file I created earlier (`{"type":"module"}`) was used for `node --check` testi…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
- Installed in 0 minutes.
- Nothing broke on the way: zero errors between clone and running.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Did not run | 50.00 | 0.04 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.18 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/indie-wiki-buddy)Questions
- Does indie-wiki-buddy run?
- Argusic could not verify that indie-wiki-buddy runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test indie-wiki-buddy?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b11d029ff0aa. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test indie-wiki-buddy?
- 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 indie-wiki-buddy take to install?
- 0 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 indie-wiki-buddy need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing indie-wiki-buddy?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for indie-wiki-buddy?
- 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.