2fa
Two Factor Authentication
Runs with mockssource: GitHubhomepageJavaScriptMITcommit 2c9ffadfc3a9
JavaScript, MIT licensed. The project labels itself: 2fa, authenticator, autofill, backup, browser extension, chrome extension, cloudflare workers and encryption.
2fa runs, with stand-ins for the services it depends on. An Argusic agent installed it in 12 minutes and hit 1 error on a clean machine with no GPU, and the whole session was recorded.
Dependencies installed, full test suite passes (77 files, 1539 tests), production build produces valid worker bundle ready for Cloudflare Workers deployment.
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 72 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.
- Wrangler CLI requires Node.js >=20.3.0, container has v18.19.1 — cannot start dev server2 minutes
- Install time
- 12 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 1 hit, 0 fixed with no human help
- How the result was proved
- npx vitest run on first attempt: 77 test files passed, 1539 tests passed, 4 skipped, 0 failures. npm run build: produced dist/worker.js (1.5 MB, parseable JS).
- Model tokens used
- 63,844
- Exact commit tested
- 2c9ffadfc3a9
- 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.
} catch(e) {
console.log('Syntax error:', e.message);
}
\"" in /work/repo
succeeded in 41ms:
Syntax error: Unexpected token 'export'
All my data is collected. Here is the final report:
**Summary**: `npm ci` installed with only engine warnings. The full test suite passed on first run …
tokens used
63,844
All my data is collected. Here is the final report:
**Summary**: `npm ci` installed with only engine warnings. The full test suite passed on first run …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 12 minutes.
- Licensed MIT, 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.
- Hit 1 error during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 2fa projects Argusic has installed and timed, 2fa was the 2nd fastest to reach a running state, and 2 of 4 reached one at all.
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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 72.00 | 0.05 |
Topics (from GitHub)
2faauthenticatorautofillbackupbrowser-extensionchrome-extensioncloudflare-workersencryptionfirefox-extensionhotpjavascriptotppwasecurityself-hostedserverlesstotptwo-factor-authenticationwebdav
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/2fa)Questions
- Does 2fa run?
- 2fa runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 12 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test 2fa?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2c9ffadfc3a9. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test 2fa?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does 2fa take to install?
- 12 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 2fa need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing 2fa?
- 1 thing broke in the recorded run. Each one, and the time it cost, is listed on this page.
- How does 2fa compare with the alternatives?
- Of the 4 2fa projects Argusic has installed and timed, 2fa was the 2nd fastest to reach a running state, and 2 of 4 reached one at all.
- Where is the evidence for 2fa?
- 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.