wooldridge
A textbook data package whose whole job is to stay installable, and whose releases prove how much work that is.
A side-by-side editorial comparison of frontmatter and projoint — release velocity, themes, recent moves, and the top alternatives to consider.
A small R parser quietly becoming format-agnostic about front matter.
frontmatter extracts and writes YAML or TOML front matter from text documents, with a C++ parser and pluggable YAML and TOML backends. Three releases across six months have taken it from read-only parsing to full roundtrip and then to inferring format automatically. Its scope is deliberately narrow: locating and delimiting the metadata block, and delegating the actual parsing to other packages.
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
projoint is an R package for analysing conjoint survey experiments, covering Qualtrics import, reshaping, and quantity-of-interest estimation with inter-rater reliability correction. Most of its release history is CRAN admission work — citation formats, DESCRIPTION fields, \value{} tags, vignette cleanups — with four tags backfilled within ninety seconds of each other on 15 July in non-monotonic version order, so neither tag order nor timestamps in this feed track the real sequence. The substantive releases are the ones fixing data-preparation bugs that silently corrupt estimates.
frontmatter extracts and writes YAML or TOML front matter from text documents, with a C++ parser and pluggable YAML and TOML backends. Three releases across six months have taken it from read-only parsing to full roundtrip and then to inferring format automatically. Its scope is deliberately narrow: locating and delimiting the metadata block, and delegating the actual parsing to other packages.
Each release widens the set of files it recognises without widening what it claims to do — standard YAML and TOML fences first, then comment-wrapped R and Python variants and PEP 723 inline script metadata, then shebang-prefixed scripts. The complementary thread is preserving what it found: format and fence type are attached as attributes so a document can be rewritten in the style it arrived in. The remaining rough edge is acknowledged in the notes, since comments and formatting inside the front matter do not survive a roundtrip.
Expect further delimiter styles as they appear in the wild, and likely work on making the roundtrip preserve comments and formatting, which the package currently flags as imperfect.
projoint is an R package for analysing conjoint survey experiments, covering Qualtrics import, reshaping, and quantity-of-interest estimation with inter-rater reliability correction. Most of its release history is CRAN admission work — citation formats, DESCRIPTION fields, \value{} tags, vignette cleanups — with four tags backfilled within ninety seconds of each other on 15 July in non-monotonic version order, so neither tag order nor timestamps in this feed track the real sequence. The substantive releases are the ones fixing data-preparation bugs that silently corrupt estimates.
The maintainer is hardening the path from raw Qualtrics export to estimate, which is where conjoint analysis quietly goes wrong. Three separate releases fix that path: dropped respondent-level weights in organize_data(), repeated-task reshaping in reshape_projoint(), and choice-to-profile mapping in 1.1.3. Each fix now arrives with regression tests and stricter validation rather than just a patch, and 1.1.3 adds an explicit .choice_map so the mapping is auditable instead of inferred.
Expect the validation-and-regression-test pattern to keep extending across the import path, with releases continuing to arrive in bursts around CRAN submission rather than on a cadence.
Other Infra & APIs 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 frontmatter or projoint.
A textbook data package whose whole job is to stay installable, and whose releases prove how much work that is.
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
See all frontmatter alternatives → · See all projoint alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. projoint 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. projoint 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 Infra & APIs products to evaluate alongside.
Top frontmatter alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "frontmatter alternatives" section above for the current picks, or visit /alternatives/frontmatter for the full list with editorial commentary on each.
Top projoint alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "projoint alternatives" section above for the current picks, or visit /alternatives/projoint for the full list with editorial commentary on each.