spsurvey
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
A side-by-side editorial comparison of pedtools and tibblify — release velocity, themes, recent moves, and the top alternatives to consider.
pedtools rewrote loop breaking and made a class of pedigrees analyzable for the first time.
pedtools is the foundation of the ped suite, holding the pedigree data structures every other package builds on. Version 2.11.0 revamped the loop breaking algorithm so founders can serve as loop breakers and one individual can break several loops, which makes likelihood calculations possible in pedigrees that previously could not be handled at all. Loop detection also became mandatory and faster, and the surrounding releases have steadily added query and construction helpers.
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
tibblify converts nested lists and JSON into rectangular tibbles using an explicit specification of the expected structure. Its 0.2.0 rewrite moved the engine to C and reset the API; 0.3.1 then added a path to generate specifications from an OpenAPI document rather than hand-writing them. 0.4.0 in May 2026 is the first release in over two years, and it is a breaking cleanup.
pedtools is the foundation of the ped suite, holding the pedigree data structures every other package builds on. Version 2.11.0 revamped the loop breaking algorithm so founders can serve as loop breakers and one individual can break several loops, which makes likelihood calculations possible in pedigrees that previously could not be handled at all. Loop detection also became mandatory and faster, and the surrounding releases have steadily added query and construction helpers.
The package has been working toward this for over a year. Version 2.8.0 replaced the igraph-based loop breaker with a custom implementation, 2.8.1 made findLoopBreakers() substantially faster in large pedigrees, and 2.11.0 rewrote the algorithm outright. The new methods ship disabled by default while downstream packages catch up, which is a deliberately staged rollout rather than a flag day. Alongside that, the additive work is small, well-scoped helpers: children2(), addSibling(), isHomozygous(), trim(), nChildren().
Expect the new loop breaking methods to become the default once pedprobr, forrel, and dvir have all shipped support for them, since the only stated reason for the opt-in flag is downstream readiness.
tibblify converts nested lists and JSON into rectangular tibbles using an explicit specification of the expected structure. Its 0.2.0 rewrite moved the engine to C and reset the API; 0.3.1 then added a path to generate specifications from an OpenAPI document rather than hand-writing them. 0.4.0 in May 2026 is the first release in over two years, and it is a breaking cleanup.
The arc runs from 'write a spec by hand' toward 'the spec comes from somewhere else'. Alongside the OpenAPI importer, guess_tspec() gained exported variants so users can override its dispatch, and untibblify() now picks up the tib_spec attribute automatically. 0.4.0's breaking change prefixes all arguments of dot-accepting functions with a period to avoid collisions with column names, softened by a once-per-session deprecation warning, and refactors the entire codebase.
The un-dotted argument forms are explicitly slated for removal, so the next release most likely completes that deprecation. Whether the 0.4.0 refactor introduced corner-case regressions is the open question the release notes themselves raise.
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 pedtools or tibblify.
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
StreamCatTools is quietly moving off web services and onto cloud-native GeoParquet
reproducible added a windowed read path so remote GeoTiffs never fully download
qcTAF is building an automated checklist for reproducible fisheries assessments, one criterion at a time
After three dormant years, rpymat returned to fix the OpenMP crash that breaks R and conda together
ieegio's first release lands electrode trajectory burning and a WebGL-free surface plot
See all pedtools alternatives → · See all tibblify alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. pedtools and tibblify 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. pedtools and tibblify 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 pedtools alternatives in Analytics are ranked by recent ship velocity. Browse the "pedtools alternatives" section above for the current picks, or visit /alternatives/pedtools for the full list with editorial commentary on each.
Top tibblify alternatives in Analytics are ranked by recent ship velocity. Browse the "tibblify alternatives" section above for the current picks, or visit /alternatives/tibblify for the full list with editorial commentary on each.