typst-gather
Extracted from Quarto's CLI, typst-gather learned to explain a dependency tree before fetching it.
Comparison · Analytics
charlatan vs qualtRics
A side-by-side editorial comparison of charlatan and qualtRics — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-packageropensci
charlatan vs qualtRics: at a glance
What is charlatan?
R's fake-data generator rebuilt its provider hierarchy so contributors can add one locale without touching the rest.
charlatan generates realistic fake data — names, addresses, phone numbers, jobs, internet artefacts — across many locales, following the same model as faker in Python and Perl. The 0.6.1 release reworked the provider class hierarchy so locale-specific providers inherit from a parent, and 0.6.2 since has been a documentation rebuild that happened to surface a duplicate Norwegian phone number pattern. Activity is sparse and bursty.
What is qualtRics?
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
qualtRics is the R client for the Qualtrics v3 API — fetching survey responses, definitions, distributions, and contact lists into tidy data frames. Version 3.3.0 migrated all_mailinglists() and fetch_mailinglist() from the deprecated Research Core Contacts endpoints to XM Directory, ahead of Qualtrics retiring the old ones on June 30, 2026. Authentication and directory discovery are handled automatically, but the new endpoints return a different data shape, so column names changed. Before that, releases had been steady maintenance for two years, mostly around how survey response archives are unpacked.
charlatan vs qualtRics: editorial side-by-side
charlatan
0.0ANALYTICS
R's fake-data generator rebuilt its provider hierarchy so contributors can add one locale without touching the rest.
◆ Current state
charlatan generates realistic fake data — names, addresses, phone numbers, jobs, internet artefacts — across many locales, following the same model as faker in Python and Perl. The 0.6.1 release reworked the provider class hierarchy so locale-specific providers inherit from a parent, and 0.6.2 since has been a documentation rebuild that happened to surface a duplicate Norwegian phone number pattern. Activity is sparse and bursty.
◆ Where it's heading
The package's value scales with locale coverage, and its releases track that: early versions added data-type providers, middle versions added locales one contributor at a time, and 0.6.1 attacked the bottleneck by restructuring the class hierarchy so a locale can override a single function. Development has effectively been handed to contributors, with maintainer releases reduced to docs rebuilds and CRAN compliance.
◆ Prediction
Expect the next substantive release to be an accumulation of contributed locales and providers arriving through the new parent-provider structure, rather than maintainer-driven feature work.
qualtRics
0.0ANALYTICS
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
◆ Current state
qualtRics is the R client for the Qualtrics v3 API — fetching survey responses, definitions, distributions, and contact lists into tidy data frames. Version 3.3.0 migrated all_mailinglists() and fetch_mailinglist() from the deprecated Research Core Contacts endpoints to XM Directory, ahead of Qualtrics retiring the old ones on June 30, 2026. Authentication and directory discovery are handled automatically, but the new endpoints return a different data shape, so column names changed. Before that, releases had been steady maintenance for two years, mostly around how survey response archives are unpacked.
◆ Where it's heading
This package's roadmap is set by Qualtrics, not by its maintainers, and the release history reads as a sequence of accommodations — endpoint changes, retired APIs, and edge cases in exported files. The team's own recurring theme is reducing surprise: caching was removed from fetch_survey() in 3.2.0 so results are never stale, error handling was standardized on retry semantics, and column mappings were made inspectable via extract_colmap(). Feature additions, when they come, are new endpoints wrapped rather than new abstractions.
◆ Prediction
With the Contacts migration complete, the next likely work is bringing the remaining Research Core-era functions onto XM Directory equivalents before Qualtrics retires more of the old surface.
Alternatives to charlatan and qualtRics
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 charlatan or qualtRics.
naijR
naijR is assembling the Nigerian reference data R analysts otherwise hand-code every time.
RBesT
RBesT is teaching its Bayesian decision rules to answer two-sided questions.
graphicalMCP
graphicalMCP is a narrow statistical tool being hardened rather than grown.
rtflite
rtflite stopped being an RTF writer and became the conversion layer for clinical table output.
git2rdata
git2rdata keeps sharpening one idea: a data frame that produces a readable git diff.
See all charlatan alternatives → · See all qualtRics alternatives →
Recent activity from charlatan and qualtRics
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoqualtRicsMailing list functions migrated to the XM Directory API ⚡
- 7mo agocharlatanDocs rebuild surfaces a duplicate Norwegian phone pattern
- 11mo agoqualtRicsZip extraction handles more special characters in survey titles
- 1y agocharlatanProvider classes restructured so locales can override single functions ⚡
- 1y agoqualtRicsFix for questions with both recoded values and variable naming
- 1y agoqualtRicsBuild and CI housekeeping alongside the 3.2.1 release
- 2y agoqualtRicsSurvey response caching removed from fetch_survey()
- 3y agoqualtRicsArgument checking refactor and include_* NA fix
- 6y agocharlatanNew locales and providers; allowed_locales() added
- 7y agocharlatanLocale naming standardised; French and Danish data corrected
- 8y agocharlatancharlatan v0.2.2
- 8y agocharlatanSix new providers broaden charlatan beyond names and addresses
Frequently asked questions
What is the difference between charlatan and qualtRics?
Both compete on the same themes — r-package, ropensci — within Analytics. charlatan and qualtRics 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.
Is charlatan better than qualtRics?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. charlatan and qualtRics 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.
What are the best alternatives to charlatan?
Top charlatan alternatives in Analytics are ranked by recent ship velocity. Browse the "charlatan alternatives" section above for the current picks, or visit /alternatives/charlatan for the full list with editorial commentary on each.
What are the best alternatives to qualtRics?
Top qualtRics alternatives in Analytics are ranked by recent ship velocity. Browse the "qualtRics alternatives" section above for the current picks, or visit /alternatives/qualtrics for the full list with editorial commentary on each.