Cronicle
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
Comparison · Infra & APIs
q2 vs Semgrep
A side-by-side editorial comparison of q2 and Semgrep — release velocity, themes, recent moves, and the top alternatives to consider.
q2 vs Semgrep: at a glance
What is q2?
Ten releases in six days, methodically porting Quarto's surface into a Rust binary.
q2 is the Quarto team's Rust reimplementation of Quarto, shipping as a statically linked single binary with signed release archives and a bundled Quarto Hub MCP server. It is explicitly marked experimental and not production-ready, and it is moving fast — ten releases between 7 and 13 August. The release notes are raw commit logs rather than curated summaries, and reading them shows a consistent programme: work items are investigated, design decisions recorded, tests written red, then implemented in numbered phases, with 'Q1 parity' as the recurring benchmark against the existing Quarto.
What is Semgrep?
Semgrep keeps spending releases on parser breadth and large-repo throughput, not new surface.
Ten consecutive releases have gone into the engine rather than the product. The recurring shape is a parser refresh (Solidity, Ruby, Dart), a scan-performance change, and a batch of correctness fixes for Pro analysis. Nothing in this window changes what a team buys Semgrep for; it changes how reliably a scan finishes on a large repository.
q2 vs Semgrep: editorial side-by-side
q2
6.3INFRA · APIS
Ten releases in six days, methodically porting Quarto's surface into a Rust binary.
◆ Current state
q2 is the Quarto team's Rust reimplementation of Quarto, shipping as a statically linked single binary with signed release archives and a bundled Quarto Hub MCP server. It is explicitly marked experimental and not production-ready, and it is moving fast — ten releases between 7 and 13 August. The release notes are raw commit logs rather than curated summaries, and reading them shows a consistent programme: work items are investigated, design decisions recorded, tests written red, then implemented in numbered phases, with 'Q1 parity' as the recurring benchmark against the existing Quarto.
◆ Where it's heading
The project is working through the original Quarto's feature surface item by item — project profiles, environment files, shortcodes in metadata, listings, callouts, crossrefs, TOC handling, aliases — while building infrastructure the original lacks, notably a numbered diagnostic catalogue (Q-2-47, Q-14-4 and so on) with a lint that requires a documentation page for every error code. Version 0.18.0's Lua filter support is the load-bearing one, since Quarto's extension ecosystem is written in Lua. Distribution choices point at the same goal: musl-static Linux builds, minisign signatures, no glibc requirement.
◆ Prediction
Expect the parity grind to continue at this cadence, with the remaining high-value Q1 features and diagnostic coverage as the visible queue. The commit logs also show npx distribution planned for the MCP server, which is the nearest thing to a stated roadmap item in these entries.
Semgrep
5.0INFRA · APIS
Semgrep keeps spending releases on parser breadth and large-repo throughput, not new surface.
◆ Current state
Ten consecutive releases have gone into the engine rather than the product. The recurring shape is a parser refresh (Solidity, Ruby, Dart), a scan-performance change, and a batch of correctness fixes for Pro analysis. Nothing in this window changes what a team buys Semgrep for; it changes how reliably a scan finishes on a large repository.
◆ Where it's heading
The performance work is converging on one problem: very large monorepos. File targeting now batches path filtering across worker domains, rule parsing shards by bytes instead of worker count, and a new Pro memory policy lets a scan trade RAM for skipping on-disk caching. Running alongside it is a quieter thread of trust work, and the 1.173.0 fix for silently dropped targets belongs to it: a file whose path filtering failed appeared in neither the findings nor the skipped list, which is the kind of gap that undermines a scan report more than any missing rule.
◆ Prediction
Expect the parser-refresh-plus-throughput cadence to continue, with the memory policy and the dependency-path output likely graduating out of experimental once large-repo users report back on them.
Alternatives to q2 and Semgrep
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either q2 or Semgrep.
Helm
Helm runs two release trains in lockstep while v3 walks toward end-of-life.
goodpractice
The R package-quality checker returns from CRAN limbo with checks you can select by category.
quarto
Quarto's editor extension is quietly becoming Positron-first while keeping VS Code parity.
pkgcache
The metadata cache under pak now speaks to authenticated and corporate repositories.
packrat
R's old dependency manager now runs on a vendored copy of its own successor.
Recent activity from q2 and Semgrep
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 17h agoq2TOC entries carry inline markup; draft banner restored
- 23h agoSemgrepSolidity parser refresh; batched targeting for very large repos
- 1d agoq2Adds alias redirect stubs and diagnostic suppression
- 2d agoq2Bumps samod and automerge; fixes indented continuations
- 2d agoq2Lua filters supported; mermaid bundled instead of CDN-loaded ⚡
- 3d agoq2Mermaid cell options, callout titles, email autolinks
- 3d agoq2Project profiles, environment files, shortcodes in metadata
- 16d agoSemgrepOpenTofu files scanned as Terraform; Ruby parser updated
- 22d agoSemgrepBuild moves to a patched OCaml compiler to stop rare crashes
- 29d agoSemgrepPro C/C++ scans skip statically-dead preprocessor branches
- 1mo agoSemgrepDart parser updated to a newer upstream version
- 1mo agoSemgrepExperimental flag exposes full paths for transitive dependency findings
Frequently asked questions
What is the difference between q2 and Semgrep?
They serve adjacent needs but don't currently overlap on shipped themes. q2 is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is q2 better than Semgrep?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. q2 is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to q2?
Top q2 alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "q2 alternatives" section above for the current picks, or visit /alternatives/q2 for the full list with editorial commentary on each.
What are the best alternatives to Semgrep?
Top Semgrep alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Semgrep alternatives" section above for the current picks, or visit /alternatives/semgrep for the full list with editorial commentary on each.