wooldridge
A textbook data package whose whole job is to stay installable, and whose releases prove how much work that is.
Comparison · Infra & APIs
ClamAV vs projoint
A side-by-side editorial comparison of ClamAV and projoint — release velocity, themes, recent moves, and the top alternatives to consider.
ClamAV vs projoint: at a glance
What is ClamAV?
Eight CVEs in one August batch — ClamAV's parser surface is the whole story.
ClamAV runs two supported lines, 1.5.x and 1.4.x, and publishes near-identical patch releases seconds apart whenever vulnerabilities land. The August pair is the largest yet in this window: eight CVEs in 1.5.4, six of them backported to 1.4.6, spanning the ZIP catalogue, GPT partition, PESpin, PDF, Mach-O and XAR parsers. Several reach back a decade or more — the PESpin overflow affects builds from 0.90 onward.
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.
ClamAV vs projoint: editorial side-by-side
ClamAV
5.0INFRA · APIS
Eight CVEs in one August batch — ClamAV's parser surface is the whole story.
◆ Current state
ClamAV runs two supported lines, 1.5.x and 1.4.x, and publishes near-identical patch releases seconds apart whenever vulnerabilities land. The August pair is the largest yet in this window: eight CVEs in 1.5.4, six of them backported to 1.4.6, spanning the ZIP catalogue, GPT partition, PESpin, PDF, Mach-O and XAR parsers. Several reach back a decade or more — the PESpin overflow affects builds from 0.90 onward.
◆ Where it's heading
Feature work has been paused since 1.5.0 last October; everything since is patch traffic against the file format parsers, and the batches are growing rather than shrinking. The August release widens the surface beyond parsing for the first time here, with a clamd STATS thread-safety bug that could disclose process memory or crash the daemon. Reporter credits increasingly come from automated discovery — Atuin, GitHub Security Lab, Trail of Bits — which suggests the find rate tracks the tooling pointed at this codebase, not new code being written.
◆ Prediction
Expect the dual-branch pattern to continue and per-batch CVE counts to stay high while automated fuzzing keeps sweeping the parser surface. These entries give no indication of a 1.6 line opening — there has been no development release since the 1.5.0 cycle.
projoint
2.5INFRA · APIS
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 ClamAV 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 ClamAV or projoint.
L1centrality
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
exametrika
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
nuggets
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
eratosthenes
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
dqcheckr
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
See all ClamAV alternatives → · See all projoint alternatives →
Recent activity from ClamAV and projoint
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 11d agoClamAVEight parser CVEs and a clamd STATS disclosure fix
- 11d agoClamAV1.4 branch takes six of the eight parser CVEs
- 17d agoprojointExplicit .choice_map guards choice-to-profile mapping
- 1mo agoprojointCRAN submission housekeeping for DESCRIPTION and examples
- 1mo agoprojointCRAN formatting pass; minor make_projoint_data() fix
- 1mo agoprojointreshape_projoint() repeated-task bug fixed; validation tightened
- 1mo agoprojointCitation metadata updated with the CRAN DOI
- 1mo agoClamAVPESpin use-after-free and PE overflow patched
- 1mo agoClamAVSame PE fixes backported to the 1.4 line
- 5mo agoClamAVHTML parser crash fixed; Rust floor raised again
- 5mo agoClamAV1.4 branch takes the HTML and TIFF parser fixes
- 5mo agoprojointorganize_data() no longer drops respondent-level weights
Frequently asked questions
What is the difference between ClamAV and projoint?
They serve adjacent needs but don't currently overlap on shipped themes. ClamAV is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 ClamAV better than projoint?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ClamAV is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 ClamAV?
Top ClamAV alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ClamAV alternatives" section above for the current picks, or visit /alternatives/clamav 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.