EDAForge
EDAForge is a data-quality auditor renamed mid-flight, still finding its CRAN footing.
Comparison · Infra & APIs
cvms vs Merge
A side-by-side editorial comparison of cvms and Merge — release velocity, themes, recent moves, and the top alternatives to consider.
cvms vs Merge: at a glance
| Feature | cvms | Merge |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | cross-validation, r-package, model-evaluation, visualization | unified api, agent handler, mcp connectors, ai gateway |
| Last editorial update | 22h ago | 15h ago |
| Website | Visit → | — |
What is cvms?
A cross-validation package whose real development has moved to its plotting function
cvms runs repeated cross-validation over model formulas and reports comparable metrics. The 2.0.0 release was a breaking correctness fix: every function accepting fold_cols mismatched training and testing data when fold indices were non-sequential, did not start at 1, or were strings, because the iteration index was compared against the raw fold value rather than its factor level index. 2.0.1 restored coefficient extraction for nnet::multinom and mixed models by supplying an environment containing the training data, and followed lme4's move of findbars() into the reformulas package.
What is Merge?
Merge is turning its weekly integration digest into an agent control plane — the news is always at the bottom.
Merge publishes one dated digest a week, and the structure is consistent: unified Accounting, ATS, CRM, File Storage and HRIS reliability work up top, then Agent Handler and Gateway at the end, where the directional changes live. The feed now also carries per-product breakout entries (Gateway, Unified, Agent Handler) that restate the same week's items in more detail rather than adding new ones. The Agent Handler catalog carries hundreds of generic MCP connectors alongside Merge's own, on shared authentication and policy, and Gateway has been accumulating model coverage, routing controls and guardrails over the same period.
cvms vs Merge: editorial side-by-side
cvms
0.0INFRA · APIS
A cross-validation package whose real development has moved to its plotting function
◆ Current state
cvms runs repeated cross-validation over model formulas and reports comparable metrics. The 2.0.0 release was a breaking correctness fix: every function accepting fold_cols mismatched training and testing data when fold indices were non-sequential, did not start at 1, or were strings, because the iteration index was compared against the raw fold value rather than its factor level index. 2.0.1 restored coefficient extraction for nnet::multinom and mixed models by supplying an environment containing the training data, and followed lme4's move of findbars() into the reformulas package.
◆ Where it's heading
Two threads run in parallel and only one is about cross-validation. The plotting function plot_confusion_matrix() has absorbed most feature work since 1.5.0 - custom gradient palettes, intensity limits, per-tile settings, dynamic font colors keyed to value thresholds, and arguments that accept functions rather than constants - to the point where a companion web application exists for using it without code. The cross-validation core, by contrast, sees maintenance: upstream compatibility fixes for pROC, ggnewscale and ggplot2, and the fold-matching correction that finally forced a major version.
◆ Prediction
Expect continued option growth in the confusion matrix plotting surface, since that is where nearly every release since 1.5.0 has spent its changes, with core cross-validation changes arriving only as upstream packages force them.
Merge
6.3INFRA · APIS
Merge is turning its weekly integration digest into an agent control plane — the news is always at the bottom.
◆ Current state
Merge publishes one dated digest a week, and the structure is consistent: unified Accounting, ATS, CRM, File Storage and HRIS reliability work up top, then Agent Handler and Gateway at the end, where the directional changes live. The feed now also carries per-product breakout entries (Gateway, Unified, Agent Handler) that restate the same week's items in more detail rather than adding new ones. The Agent Handler catalog carries hundreds of generic MCP connectors alongside Merge's own, on shared authentication and policy, and Gateway has been accumulating model coverage, routing controls and guardrails over the same period.
◆ Where it's heading
The through-line is that Merge is repositioning from data plumbing to the layer agents pass through. Each week adds either reach (more connectors, more tools per connector, more models) or control (guardrails, per-project policy, access configuration). This window is reach-and-efficiency: the GitHub connector expanded to 145 tools, Outlook payloads were cut substantially, and Gateway guardrails became configurable per project rather than per account.
◆ Prediction
Expect the per-project granularity applied to guardrails to spread to the rest of Gateway's controls, and the connector catalog to keep absorbing hosted third-party MCP servers the way Axiom was added.
Alternatives to cvms and Merge
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 cvms or Merge.
inti
inti keeps compounding small statistics and publishing tools for plant-science labs.
ackwards
ackwards turns a niche factor-analysis method into a figure-ready toolchain.
FishSET
FishSET 2.0 rebuilds the estimation core on RTMB and retires the 1.0 API.
Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Recent activity from cvms and Merge
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoMergeGitHub connector hits 145 tools; Gateway adds per-project guardrails
- 19d agoMergeHundreds of generic MCP connectors land in Agent Handler ⚡
- 26d agoMergeLink setup flow becomes configurable per integration
- 1mo agoMergeEmbedded Routing Stack gives Gateway per-customer model controls
- 1mo agoMergeGateway breakout page for the week already covered by Week 2
- 1mo agoMergeUnified breakout page for the week already covered by Week 3
- 2mo agocvmsCoefficient extraction restored for multinom and mixed models
- 9mo agocvmsBreaking fix for mismatched folds with non-sequential fold IDs
- 11mo agocvmsTest compatibility with pROC 1.19 and a deprecation warning fix
- 1y agocvmsConfusion matrix fonts and colors can now be computed from the values
- 1y agocvmsTile intensity by row or column percentages
- 1y agocvmsMultinom coefficient extraction fix after a parameters update
Frequently asked questions
What is the difference between cvms and Merge?
They serve adjacent needs but don't currently overlap on shipped themes. Merge is currently shipping more aggressively (velocity 6.3 vs 0.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 cvms better than Merge?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Merge is currently shipping more aggressively (velocity 6.3 vs 0.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 cvms?
Top cvms alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "cvms alternatives" section above for the current picks, or visit /alternatives/cvms for the full list with editorial commentary on each.
What are the best alternatives to Merge?
Top Merge alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Merge alternatives" section above for the current picks, or visit /alternatives/merge-dev for the full list with editorial commentary on each.