← Back to home
Comparison · Analytics

ichimoku vs vellum

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

ichimoku vs vellum: at a glance

Featureichimokuvellum
SectorAnalyticsAnalytics
Velocity score0.05.0
Sparks · 30d00
Top themesfinancial-charting, technical-analysis, dependency-reduction, oandar-graphics, rendering-engine, linting, accessibility
Last editorial update2h ago52m ago
WebsiteVisit →Visit →

What is ichimoku?

A cloud-chart package quietly swapping its dependencies for its maintainer's own libraries.

ichimoku implements Ichimoku Kinko Hyo cloud charts, strategy backtesting and an OANDA data interface for R. Recent releases are almost entirely plumbing: 1.5.7 drops RcppSimdJson in favor of secretbase for JSON parsing, following earlier releases that moved hashing to secretbase and raised the nanonext and mirai floors. The charting and strategy surface has been stable since the 1.5.0 line.

Read the full ichimoku trajectory →

What is vellum?

vellum's bugs are now found by using it, not testing it — the downstream grammar is doing the QA.

The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.

Read the full vellum trajectory →

ichimoku vs vellum: editorial side-by-side

I
ichimoku
ANALYTICS
0.0

A cloud-chart package quietly swapping its dependencies for its maintainer's own libraries.

◆ Current state

ichimoku implements Ichimoku Kinko Hyo cloud charts, strategy backtesting and an OANDA data interface for R. Recent releases are almost entirely plumbing: 1.5.7 drops RcppSimdJson in favor of secretbase for JSON parsing, following earlier releases that moved hashing to secretbase and raised the nanonext and mirai floors. The charting and strategy surface has been stable since the 1.5.0 line.

◆ Where it's heading

The visible arc is consolidation onto the maintainer's own package family — secretbase for hashing and now JSON, nanonext and mirai for concurrency — which steadily removes third-party and Rcpp-based dependencies from the install chain. Feature work is sporadic and narrow when it comes: a faster POSIXct formatter exported as a utility, a multi-session option for the Shiny app, and a fix for asymmetric strategies that failed to emit a final entry signal.

◆ Prediction

Expect further dependency consolidation as the sibling packages gain capabilities, with ichimoku adopting them shortly after release rather than shipping new charting features.

V
vellum
ANALYTICS
5.0

vellum's bugs are now found by using it, not testing it — the downstream grammar is doing the QA.

◆ Current state

The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.

◆ Where it's heading

The pivotal detail is stated outright in 0.6.3 — the first bug in the series found by using the engine from vellumplot rather than testing it in isolation. Every release since names the downstream as the source: the contrast rule's false positives, the lint rules that fired on all five sample plots, the keyed roundrect batch. A rendering engine with a real grammar built on top of it is now getting the integration coverage that unit tests structurally cannot provide, and the fixes are converging on one theme: the measurement path and the draw path must not drift.

◆ Prediction

Expect the release rate to fall as the vellumplot integration surface is exhausted, with remaining work concentrated in the lint rule set now that it is meant to gate builds rather than just inform.

Alternatives to ichimoku and vellum

Other Analytics 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 ichimoku or vellum.

See all ichimoku alternatives → · See all vellum alternatives →

Recent activity from ichimoku and vellum

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

  1. 11d agovellumLinter grows to 20 rules and stops firing on every plot
  2. 13d agovellumAnimated SVGs no longer blink once and vanish or play in reverse
  3. 13d agovellumPick table now reports device pixels instead of two coordinate systems
  4. 14d agovellumContrast rule stops flagging every plot; gridlines become PDF artifacts
  5. 14d agovellumgrobwidth and grobheight now measure wrapped text, not the unwrapped line
  6. 14d agovellumKeyed roundrect becomes a real batch after downstream integration exposes it
  7. 2mo agoichimokuJSON parsing moves from RcppSimdJson to secretbase
  8. 1y agoichimokuFaster POSIXct formatting exported as a utility
  9. 1y agoichimokuMultiple concurrent sessions in the OANDA Shiny app
  10. 1y agoichimokuAsymmetric strategies now emit their final entry signal
  11. 2y agoichimokusecretbase floor raised to 1.0.0
  12. 2y agoichimokuArchive verification reverts to SHA256

Frequently asked questions

What is the difference between ichimoku and vellum?

They serve adjacent needs but don't currently overlap on shipped themes. vellum 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 ichimoku better than vellum?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. vellum 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 Analytics products to evaluate alongside.

What are the best alternatives to ichimoku?

Top ichimoku alternatives in Analytics are ranked by recent ship velocity. Browse the "ichimoku alternatives" section above for the current picks, or visit /alternatives/ichimoku for the full list with editorial commentary on each.

What are the best alternatives to vellum?

Top vellum alternatives in Analytics are ranked by recent ship velocity. Browse the "vellum alternatives" section above for the current picks, or visit /alternatives/vellum-r for the full list with editorial commentary on each.