0.1.22: the graph engine ships, and answers in a table
cqx query has worked for four releases and been switched off in every
binary anybody could download. CI built it with --features zega to prove it
compiled and the release built it without, so --zql and --named were
refused everywhere they mattered. They are on now; it costs about 1.2 MB.
And the answer is readable. It printed Row { fields: {...} } — Rust's
derived Debug over a HashMap, so the columns came out in a different order
every run and a reader had to hunt for the field they asked for. It is a
table now, in the order the RETURN clause named, because the clause's own
text is exactly what the engine keyed the map by. --json gives the same
rows as data.
Long cells are cut at forty-four characters and the first forty rows are shown, because past that a terminal is not the tool.
Merge pull request #7 from samifouad/claude/cqx-action
Score zega with cqx on every pull request
Merge pull request #1169 from dekaruntime/claude/cqx-action
cqx as an action, and an installer instead of a filename
Merge pull request #304 from dekaruntime/claude/cqx-action
cqx as an action, and an installer instead of a filename
0.1.21: say which files were read
Code scanning showed "no summary of scanned files reported by cqx", which reads as a tool that did not look rather than one that found nothing there. SARIF has a place for it and we were leaving it empty.
The run now lists every path the scan read as an analysisTarget — 58 of them for cqx itself, against 24 results.
0.1.20: what the run cost, in the report
The terminal has always printed "58 files · 7,802 lines · 0.1s" and the report carried only the line count, so anything drawing from the JSON could not say the same sentence — the card on a pull request was reduced to a line count and a ref.
The report now carries scan: files, lines, milliseconds, and the version
that produced it.