ngx-scanner

Angular QR code, Barcode, DataMatrix, scanner component using ZXing.

Runssource: GitHubhomepageTypeScriptMITcommit db43c139ec15

TypeScript, MIT licensed. The project labels itself: angular, barcode, camera, demo, hacktoberfest, qr code, scanner and sponsors.

ngx-scanner runs. An Argusic agent installed it in 10 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All 6 Angular/Karma unit tests pass (1 for the scanner library component, 5 for the demo app), and the library builds to dist/zxing-scanner via ng-packagr.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
1
last tested
stars
666
forks
232
open issues
89
watchers
21
size
10 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 ngx-scanner, 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.

  • No Chrome browser installed in container3 minutes
  • Node.js v18.19.1 too old for Angular CLI 22 (requires v22.22.3+)1 minute
  • Angular CLI detected yarn not in PATH, refused to run1 minute
  • Chrome crashpad_handler binary not executable (rw-rw-r--)1 minute
  • Chrome sandbox unusable (no user namespaces in container)1 minute
  • npm install failed with peer dependency conflict on @angular/animations1 minute
Install time
10 minutes
Cold machine to finish
10 minutes
Errors hit and fixed
6 hit, 6 fixed with no human help
How the result was proved
npx ng test zxing-scanner --watch=false --browsers=ChromeHeadlessNoSandbox returned 'TOTAL: 1 SUCCESS'; npx ng test zxing-scanner-demo --watch=false --browsers=ChromeHeadlessNoSandbox returned 'TOTAL: 5 SUCCESS'
Model tokens used
330,648
Exact commit tested
db43c139ec15
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.

All tests pass and the library builds successfully. Here's the final report:
**Install**: `npm install --legacy-peer-deps` (1372 packages).
**Build**: `ng build zxing-scanner --configuration production` succeeded.
**Tests**: Library: 1/1 PASS. Demo: 5/5 PASS.
**Total time**: ~10 minutes.
**Errors encountered and fixed:**
1. **Node.js v18 too old** → downloaded and used Node.js v22.22.3 binary
2. **Angular CLI required yarn** → installed yarn via npm
3. **No Chrome browser** → downloaded Chrome for Testing via python3 (puppeteer's installer lacked …
4. **Chrome crashpad_handler not executable** → chmod 755
5. **Chrome sandbox unavailable in container** → added `ChromeHeadlessNoSandbox` custom launcher wi…
6. **npm peer dependency conflict** → used `--legacy-peer-deps`

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.
  • Recovered from all 6 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 MIT, as reported by its host.

What did not, or is not known

  • Took 10 minutes to install, slower than the median of the 9 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 10 angular projects Argusic has installed and timed, ngx-scanner was the 9th fastest to reach a running state, and 10 of 10 reached one at all.

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 10 minutes after the clone.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.03

Topics (from GitHub)

angularbarcodecamerademohacktoberfestqr-codescannersponsorswikizxing

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/ngx-scanner.svg)](https://argusic.com/subject/ngx-scanner)

Questions

Does ngx-scanner run?
Yes. ngx-scanner runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test ngx-scanner?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit db43c139ec15. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test ngx-scanner?
The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ngx-scanner 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 ngx-scanner need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ngx-scanner?
6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does ngx-scanner compare with the alternatives?
Of the 10 angular projects Argusic has installed and timed, ngx-scanner was the 9th fastest to reach a running state, and 10 of 10 reached one at all.
Where is the evidence for ngx-scanner?
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