← Back to home
Comparison · Infra & APIs

kwb.pkgbuild vs projoint

A side-by-side editorial comparison of kwb.pkgbuild and projoint — release velocity, themes, recent moves, and the top alternatives to consider.

kwb.pkgbuild vs projoint: at a glance

Featurekwb.pkgbuildprojoint
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themesr, github actions, ci, package templatesconjoint-analysis, survey-research, qualtrics, cran
Last editorial update2d ago1h ago
WebsiteVisit →Visit →

What is kwb.pkgbuild?

kwb.pkgbuild's CI templates went four years without a refresh, then had to be rebuilt for current runners

kwb.pkgbuild automates R package setup at Kompetenzzentrum Wasser Berlin to a house style, and its main deliverable is the GitHub Actions templates it installs into new packages. Between October 2022 and May 2026 there were no releases. During that gap the templates aged past the point of working on current GitHub-hosted runners.

Read the full kwb.pkgbuild trajectory →

What is projoint?

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.

Read the full projoint trajectory →

kwb.pkgbuild vs projoint: editorial side-by-side

K
kwb.pkgbuild
INFRA · APIS
0.0

kwb.pkgbuild's CI templates went four years without a refresh, then had to be rebuilt for current runners

◆ Current state

kwb.pkgbuild automates R package setup at Kompetenzzentrum Wasser Berlin to a house style, and its main deliverable is the GitHub Actions templates it installs into new packages. Between October 2022 and May 2026 there were no releases. During that gap the templates aged past the point of working on current GitHub-hosted runners.

◆ Where it's heading

0.3.0 is a catch-up release rather than a direction change: action versions bumped to checkout@v5, upload-artifact@v4 and codecov-action@v5 to clear the Node.js 20 deprecation, deprecated r-lib/actions@master references replaced with @v2, the retired ubuntu-20.04 runner swapped for ubuntu-latest, and the archived r-hub/sysreqs step replaced with setup-r-dependencies@v2, which also brings dependency caching. One fix stands out: a stale conditional comparing runner.os to the string 'Linux (no, try without!)' had been silently disabling the Linux system-dependency step.

◆ Prediction

For a package whose product is CI configuration, releases will keep tracking GitHub Actions deprecations — the notes already cite the Node.js 20 removal date. The four-year gap suggests updates arrive when something breaks rather than on a schedule.

P
projoint
INFRA · APIS
2.5

projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to kwb.pkgbuild and projoint

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 kwb.pkgbuild or projoint.

See all kwb.pkgbuild alternatives → · See all projoint alternatives →

Recent activity from kwb.pkgbuild and projoint

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 17d agoprojointExplicit .choice_map guards choice-to-profile mapping
  2. 1mo agoprojointCRAN submission housekeeping for DESCRIPTION and examples
  3. 1mo agoprojointCRAN formatting pass; minor make_projoint_data() fix
  4. 1mo agoprojointreshape_projoint() repeated-task bug fixed; validation tightened
  5. 1mo agoprojointCitation metadata updated with the CRAN DOI
  6. 3mo agokwb.pkgbuildGitHub Actions templates rebuilt for current runners
  7. 5mo agoprojointorganize_data() no longer drops respondent-level weights
  8. 3y agokwb.pkgbuildRepair CI workflows broken by upstream branch removal
  9. 4y agokwb.pkgbuildWindows becomes default OS for pkgdown and coverage workflows
  10. 4y agokwb.pkgbuildBugfix release
  11. 4y agokwb.pkgbuildRelease with no documented changes
  12. 4y agokwb.pkgbuildFix R CMD check workflow by adding GITHUB_PAT

Frequently asked questions

What is the difference between kwb.pkgbuild and projoint?

They serve adjacent needs but don't currently overlap on shipped themes. 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.

Is kwb.pkgbuild better than projoint?

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.

What are the best alternatives to kwb.pkgbuild?

Top kwb.pkgbuild alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "kwb.pkgbuild alternatives" section above for the current picks, or visit /alternatives/kwb-pkgbuild for the full list with editorial commentary on each.

What are the best alternatives to projoint?

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.