← Back to home
Comparison · Infra & APIs

rgm vs Semgrep

A side-by-side editorial comparison of rgm and Semgrep — release velocity, themes, recent moves, and the top alternatives to consider.

rgm vs Semgrep: at a glance

FeaturergmSemgrep
SectorInfra & APIsInfra & APIs
Velocity score0.05.0
Sparks · 30d00
Top themesmicrobiome, graphical-models, bayesian-inference, cran-maintenancestatic-analysis, language-coverage, scan-performance, large-repo-scaling
Last editorial update1h ago5d ago
WebsiteVisit →Visit →

What is rgm?

A microbiome network model that got itself un-archived by deleting the dependency that killed it.

rgm implements the random graphical model for microbiome interactions across related environments, published in JABES in 2026. The package was archived from CRAN in February 2026 because of its dependency on huge; the recovery release drops that dependency entirely, which cost it the graphical-lasso warm start that used to seed the initial graph — the default is now an empty graph, with warm starts left to the user. A post-processing function returning ggplot diagnostics arrived in the same release.

Read the full rgm trajectory →

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.

Read the full Semgrep trajectory →

rgm vs Semgrep: editorial side-by-side

R
rgm
INFRA · APIS
0.0

A microbiome network model that got itself un-archived by deleting the dependency that killed it.

◆ Current state

rgm implements the random graphical model for microbiome interactions across related environments, published in JABES in 2026. The package was archived from CRAN in February 2026 because of its dependency on huge; the recovery release drops that dependency entirely, which cost it the graphical-lasso warm start that used to seed the initial graph — the default is now an empty graph, with warm starts left to the user. A post-processing function returning ggplot diagnostics arrived in the same release.

◆ Where it's heading

Three tags shipped inside two hours on one day, and the notes are candid about why: 1.1.0 held the actual work but was never released, 1.2.0 restated it under a higher version to signal the size of the change, and 1.2.1 answered CRAN pre-test feedback. Beyond the archival recovery, the visible work is housekeeping that had accumulated — a shadowed rmvnorm() definition, roxygen import tags that were silently emitting nothing, leftover C++ template scaffolding, and build artifacts under version control. The diagnostics function is the only genuinely new user-facing capability in the window.

◆ Prediction

The immediate task was restoring availability, and that is done; the open question the entries raise is whether losing the graphical-lasso warm start affects convergence in practice, which the new diagnostic plots are positioned to answer.

S
Semgrep
INFRA · APIS
5.0

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 rgm 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 rgm or Semgrep.

See all rgm alternatives → · See all Semgrep alternatives →

Recent activity from rgm and Semgrep

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 5d agoSemgrepSolidity parser refresh; batched targeting for very large repos
  2. 21d agoSemgrepOpenTofu files scanned as Terraform; Ruby parser updated
  3. 27d agoSemgrepBuild moves to a patched OCaml compiler to stop rare crashes
  4. 1mo agoSemgrepPro C/C++ scans skip statically-dead preprocessor branches
  5. 1mo agoSemgrepDart parser updated to a newer upstream version
  6. 1mo agoSemgrepExperimental flag exposes full paths for transitive dependency findings
  7. 3mo agorgmJournal DOI replaces the preprint; promotional wording removed
  8. 3mo agorgmBack on CRAN after dropping the dependency that caused archival
  9. 3mo agorgmUnreleased twin of the CRAN recovery release
  10. 2y agorgmFirst release: simulation, estimation and post-processing

Frequently asked questions

What is the difference between rgm 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 rgm 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 rgm?

Top rgm alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rgm alternatives" section above for the current picks, or visit /alternatives/rgm 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.