spsurvey
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
Comparison · Analytics
KLINK vs tibblify
A side-by-side editorial comparison of KLINK and tibblify — release velocity, themes, recent moves, and the top alternatives to consider.
KLINK vs tibblify: at a glance
What is KLINK?
Forensic kinship testing with linked STR markers, now peer-reviewed and taking data from anywhere.
KLINK is a Shiny application and R package for kinship testing that accounts for linkage between STR markers, rather than treating all markers as independent. The built-in genetic map covers 50 common STR markers, pairs them dynamically after data loads, and lets the user set the maximum distance at which a pair counts as linked. Custom marker maps can now arrive as Excel files including KLINK's own download files, and a paper describing the tool was published in FSI:Genetics in 2026.
What is tibblify?
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.
KLINK vs tibblify: editorial side-by-side
KLINK
2.5ANALYTICS
Forensic kinship testing with linked STR markers, now peer-reviewed and taking data from anywhere.
◆ Current state
KLINK is a Shiny application and R package for kinship testing that accounts for linkage between STR markers, rather than treating all markers as independent. The built-in genetic map covers 50 common STR markers, pairs them dynamically after data loads, and lets the user set the maximum distance at which a pair counts as linked. Custom marker maps can now arrive as Excel files including KLINK's own download files, and a paper describing the tool was published in FSI:Genetics in 2026.
◆ Where it's heading
The direction is from fixed panel toward general instrument. Hard-coded linkage pairs gave way to dynamic pairing, the built-in map grew from 18 to 50 markers, the map itself was then moved out to the norSTR package, and the app now accepts custom maps in several file formats and decimal conventions. Method capability tracks the upstream pedsuite rather than KLINK itself: special lumping in pedprobr and pedmut is what allowed complex mutation models in common pedigrees, and the newest release pins pedtools 2.11.0 and pedprobr 1.1.0 for faster likelihoods and better handling of looped pedigrees. Much of the remaining work is unglamorous casework ergonomics, replacing stray Norwegian text in Excel output, controlling table heights, fixing karyogram colours.
◆ Prediction
With the map externalised and custom maps loading from multiple formats, the likeliest next step is broader marker-panel coverage through norSTR rather than changes in KLINK itself. Method gains should continue to arrive as pedprobr and pedmut version bumps.
tibblify
0.0ANALYTICS
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to KLINK and tibblify
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 KLINK or tibblify.
StreamCatTools
StreamCatTools is quietly moving off web services and onto cloud-native GeoParquet
reproducible
reproducible added a windowed read path so remote GeoTiffs never fully download
qcTAF
qcTAF is building an automated checklist for reproducible fisheries assessments, one criterion at a time
rpymat
After three dormant years, rpymat returned to fix the OpenMP crash that breaks R and conda together
ieegio
ieegio's first release lands electrode trajectory burning and a WebGL-free surface plot
See all KLINK alternatives → · See all tibblify alternatives →
Recent activity from KLINK and tibblify
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoKLINKExcel marker maps, more robust map loading, and a published paper
- 3mo agotibblifyFix type mismatch in C code
- 3mo agotibblifyDot-prefixed arguments and a full internal refactor
- 3mo agoKLINKIn-app help pages, a mutation-model setting, and clearer controls
- 1y agoKLINKComplex mutation models become usable via upstream special lumping
- 1y agoKLINKDownload fix for XML initials containing hyphens
- 1y agoKLINKUnlinked report picks the higher-PIC marker from each pair
- 2y agoKLINKMarkers pair dynamically against a 50-marker map, replacing hard-coded pairs ⚡
- 2y agotibblifyparse_openapi_spec() generates tibblify specs from API documentation ⚡
- 3y agotibblifyRecursive specs, transform control and memory fixes
- 4y agotibblifyEngine rewritten in C with a renamed specification API ⚡
Frequently asked questions
What is the difference between KLINK and tibblify?
They serve adjacent needs but don't currently overlap on shipped themes. KLINK is currently shipping more aggressively (velocity 2.5 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 KLINK better than tibblify?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. KLINK is currently shipping more aggressively (velocity 2.5 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 KLINK?
Top KLINK alternatives in Analytics are ranked by recent ship velocity. Browse the "KLINK alternatives" section above for the current picks, or visit /alternatives/klink for the full list with editorial commentary on each.
What are the best alternatives to tibblify?
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.