fillpattern
Pattern fills for ggplot2, hardened against the ways users write sizes
A side-by-side editorial comparison of dynwrap and invasimapr — release velocity, themes, recent moves, and the top alternatives to consider.
A dormant trajectory-inference wrapper wakes up for maintenance only
dynwrap is the dynverse component that wraps single-cell trajectory inference methods behind a common interface, handling containerised method execution and the trajectory data model. The visible history is dominated by a burst of feature work in 2019 and then near-silence: the only recent release, v1.3.0, is a package modernisation with a minimum-version bump and no user-facing capability. The three entries in the feed span seven years.
invasimapr halved its install size and became citable; the science stayed put.
invasimapr estimates species invasiveness and site invasibility from trait, environmental and resident-community data, exposing a traits → competition → invasion-fitness pipeline behind seven high-level wrappers. Its three releases are all packaging and standards work: a first citable archive in June 2026, then a maturity release bringing it in line with the B-Cubed software development guide. The one behavioral addition in that release is an opt-in standardise_inputs argument on compute_invasion_fitness(), off by default.
dynwrap is the dynverse component that wraps single-cell trajectory inference methods behind a common interface, handling containerised method execution and the trajectory data model. The visible history is dominated by a burst of feature work in 2019 and then near-silence: the only recent release, v1.3.0, is a package modernisation with a minimum-version bump and no user-facing capability. The three entries in the feed span seven years.
The direction is custodial rather than developmental. The 2019 releases built out the substance — RNA velocity in the wrapper, velocity-oriented topologies, directed geodesic distances, Singularity 3.0 and sparse matrices throughout — and nothing since has extended it. The 2026 release reads as keeping the package installable against a modern R toolchain, which is what a maintained dependency of a benchmark suite needs rather than what an actively developed tool looks like.
On this evidence, expect further releases to be compatibility maintenance triggered by R or dependency changes; the entries give no indication of resumed feature work.
invasimapr estimates species invasiveness and site invasibility from trait, environmental and resident-community data, exposing a traits → competition → invasion-fitness pipeline behind seven high-level wrappers. Its three releases are all packaging and standards work: a first citable archive in June 2026, then a maturity release bringing it in line with the B-Cubed software development guide. The one behavioral addition in that release is an opt-in standardise_inputs argument on compute_invasion_fitness(), off by default.
The pressure is toward being installable and auditable rather than more capable — install slimmed from roughly 100 MB to 56 MB, R CMD check warnings and notes resolved, sp moved to Suggests, a Darwin Core-aligned data dictionary added, and a Zenodo concept DOI with CITATION.cff, codemeta.json and .zenodo.json. The package moves in lockstep with its B-Cubed sibling dissmapr, tagged within minutes of each other at both 0.1.0 and 0.2.1, which points at project-level standards deadlines rather than independent release decisions. Trait dispersion metrics and scenario exploration remain on the roadmap.
Standards compliance is now complete and the roadmap names functional trait dispersion metrics and scenario exploration tools, so the next release is the first that can plausibly be about invasion ecology rather than packaging.
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 dynwrap or invasimapr.
Pattern fills for ggplot2, hardened against the ways users write sizes
gcube's recent releases are all packaging metadata, not simulation code
The R port of Quinlan's Cubist gets reproducibility fixes, not new modelling
ggstats keeps widening what a coefficient or Likert plot can be
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
State-space data simulation for R, filled in one function at a time
See all dynwrap alternatives → · See all invasimapr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dynwrap and invasimapr are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dynwrap and invasimapr are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top dynwrap alternatives in Analytics are ranked by recent ship velocity. Browse the "dynwrap alternatives" section above for the current picks, or visit /alternatives/dynwrap for the full list with editorial commentary on each.
Top invasimapr alternatives in Analytics are ranked by recent ship velocity. Browse the "invasimapr alternatives" section above for the current picks, or visit /alternatives/invasimapr for the full list with editorial commentary on each.