hQuery.php

An extremely fast web scraper that parses megabytes of invalid HTML in a blink of an eye. PHP5.3+, no dependencies.

Runssource: GitHubhomepagePHPMITcommit 50a9f211b47e

PHP, MIT licensed. The project labels itself: broken html, crawler, css selectors, domcrawler, fast, hquery, html and html parser.

hQuery.php runs. An Argusic agent installed it in 9 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

hQuery.php library installs, autoloads, and parses HTML via fromHTML() and find()/text() selectors; all 27 unit tests pass on PHP 8.4.1 via FrankenPHP static binary.

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.07 (measured)
recorded runs
1
last tested
stars
358
forks
69
open issues
21
watchers
22
size
4 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 hQuery.php, 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 PHP binary installed in container3 minutes
  • phpunit not in composer require-dev2 minutes
  • SSL cert failure downloading composer installer via copy()1 minute
Install time
9 minutes
Cold machine to finish
7 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
vendor/bin/phpunit -c tests/phpunit.xml exited 0 with 27 tests and 323 assertions passed; also verified fromHTML/find/text() work via inline PHP script
Model tokens used
213,723
Exact commit tested
50a9f211b47e
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.

- Ran `composer install` which pulled Symfony DOM Crawler and CSS Selector dev dependencies.
- Added `phpunit/phpunit` ^12.0 as a dev dependency (required for PHP 8.4).
**First-run issues:**
1. **No PHP binary** - Fixed by downloading FrankenPHP static binary and creating a `php` wrapper.
2. **SSL certificate verification failed** during Composer installer download - Fixed by downloadin…
3. **Missing phpunit** - The project's `composer.json` doesn't list phpunit in require-dev; the tes…
**Test Results:**
- `vendor/bin/phpunit tests/` — **27 tests, 323 assertions, all OK**
- 2 warnings about missing optional PSR-7 HTTP discovery packages (not used by core functionality)
- Verified basic parsing works via a quick PHP script: `fromHTML()`, `find()`, `text()` all work co…
```
```

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.
  • Installed in 9 minutes.
  • Recovered from all 3 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

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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

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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.07

Topics (from GitHub)

broken-htmlcrawlercss-selectorsdomcrawlerfasthqueryhtmlhtml-parserinvalid-htmljquery-likejquery-selectorsparserphppsr-0psr-4scraperselectorsxmlxml-parser

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/hQuery.php.svg)](https://argusic.com/subject/hquery-php)

Questions

Does hQuery.php run?
Yes. hQuery.php runs. Argusic installed and launched it on a clean machine in 9 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test hQuery.php?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 50a9f211b47e. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test hQuery.php?
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 hQuery.php take to install?
9 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 hQuery.php need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing hQuery.php?
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.
Where is the evidence for hQuery.php?
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