Cronicle
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
Comparison · Infra & APIs
evaluate vs Semgrep
A side-by-side editorial comparison of evaluate and Semgrep — release velocity, themes, recent moves, and the top alternatives to consider.
evaluate vs Semgrep: at a glance
What is evaluate?
The engine under every knitted R document reached 1.0 by making evaluation behave like the console.
evaluate captures the output, plots, messages and conditions produced by running R code, and it is the layer knitr and R Markdown sit on. The 1.0.0 release changed core semantics — multi-expression input now stops at the first error — and gave results a real class. Since then, releases have been graphics-focused: ragg-based capture when available, grid plot fixes, and a patch for ggplot2 4.0.0.
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.
evaluate vs Semgrep: editorial side-by-side
evaluate
0.0INFRA · APIS
The engine under every knitted R document reached 1.0 by making evaluation behave like the console.
◆ Current state
evaluate captures the output, plots, messages and conditions produced by running R code, and it is the layer knitr and R Markdown sit on. The 1.0.0 release changed core semantics — multi-expression input now stops at the first error — and gave results a real class. Since then, releases have been graphics-focused: ragg-based capture when available, grid plot fixes, and a patch for ggplot2 4.0.0.
◆ Where it's heading
The package is being tightened rather than expanded. 1.0.0 removed complexity it could not justify, deprecated include_timing, dropped a function testing for an object it never created, and aligned error behaviour with the console; 1.0.4 then moved plot capture toward a faster, more capable device. The recurring theme is reliability of output capture across environments, which is exactly what a document-rendering substrate needs and what local_reproducible_output() exists to enforce.
◆ Prediction
Expect continued fast-follow patches keyed to graphics-stack releases — ggplot2 and ragg in particular — rather than new API surface.
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 evaluate 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 evaluate 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.
q2
Ten releases in six days, methodically porting Quarto's surface into a Rust binary.
pkgcache
The metadata cache under pak now speaks to authenticated and corporate repositories.
See all evaluate alternatives → · See all Semgrep alternatives →
Recent activity from evaluate and Semgrep
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23h agoSemgrepSolidity parser refresh; batched targeting for very large repos
- 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
- 11mo agoevaluatePatch for ggplot2 4.0.0 support
- 1y agoevaluatePlot capture moves to ragg when available
- 1y agoevaluateFix for rlang::abort() inside evaluate()
- 1y agoevaluate1.0 stops at the first error and gives results a class ⚡
- 2y agoevaluateSource handler gains access to the parsed call
Frequently asked questions
What is the difference between evaluate and Semgrep?
They serve adjacent needs but don't currently overlap on shipped themes. Semgrep is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 evaluate better than Semgrep?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Semgrep is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 evaluate?
Top evaluate alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "evaluate alternatives" section above for the current picks, or visit /alternatives/evaluate 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.