rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
checkhelper vs LightLogR
A side-by-side editorial comparison of checkhelper and LightLogR — release velocity, themes, recent moves, and the top alternatives to consider.
checkhelper vs LightLogR: at a glance
What is checkhelper?
checkhelper grew from a check wrapper into a CRAN pre-submission auditor.
1.0.0 added a whole audit_* family — audit_downloads(), audit_description(), audit_dontrun() and audit_citation() — each parsing package source statically and returning a tibble of hits paired with a suggested fix. The package is now defending that position: 1.0.1 rc1 is a submission candidate answering a CRAN archival notice, after roxygen2 8.x moved DESCRIPTION's RoxygenNote field and broke a find_missing_tags() test fixture.
What is LightLogR?
Wearable light-exposure data gets circular time and versioned device formats
LightLogR ingests recordings from wearable light loggers and optical radiation dosimeters, and its release notes are lopsided: four of the six most recent tags are one-line merge stubs while 0.10.0 carries several thousand words. That release is where the package sits — dataset-wide summary tables, a version argument on the importers, and time of day handled as a circular quantity.
checkhelper vs LightLogR: editorial side-by-side
checkhelper
2.5INFRA · APIS
checkhelper grew from a check wrapper into a CRAN pre-submission auditor.
◆ Current state
1.0.0 added a whole audit_* family — audit_downloads(), audit_description(), audit_dontrun() and audit_citation() — each parsing package source statically and returning a tibble of hits paired with a suggested fix. The package is now defending that position: 1.0.1 rc1 is a submission candidate answering a CRAN archival notice, after roxygen2 8.x moved DESCRIPTION's RoxygenNote field and broke a find_missing_tags() test fixture.
◆ Where it's heading
The design commitment is static analysis — AST walks via getParseData(), line-by-line Rd reading, no eval() and no namespace loading — so the tool can report on a package it never runs. That commitment is what made the roxygen2 8.x break survivable: the audit pipeline itself was verified correct under 8.1.0 and only the test scaffolding had to go, now guarded by a dedicated regression test. fix_globals(write = TRUE) is being sanded down in parallel, no longer flattening per-function grouping comments or writing a degenerate empty globalVariables() shell.
◆ Prediction
The immediate move is the 1.0.1 submission itself, clearing the archival notice. Beyond that, each additional CRAN incoming-check rule remains a candidate for another audit_* function; the open question these notes still leave is whether the family ever gets a single combined entry point.
LightLogR
0.0INFRA · APIS
Wearable light-exposure data gets circular time and versioned device formats
◆ Current state
LightLogR ingests recordings from wearable light loggers and optical radiation dosimeters, and its release notes are lopsided: four of the six most recent tags are one-line merge stubs while 0.10.0 carries several thousand words. That release is where the package sits — dataset-wide summary tables, a version argument on the importers, and time of day handled as a circular quantity.
◆ Where it's heading
The arc runs from reading files off N devices toward modelling the awkward shapes of chronobiology data. Circular conversion lets bedtimes crossing midnight average correctly; remove_partial_data() can demand a minimum duration rather than a fraction of a known total; add_states() takes Interval objects so sleep-scoring output flows straight in. The device side hardens in parallel — supported_versions() exists because a VEET firmware release changed the file format mid-life.
◆ Prediction
The version switch currently covers VEET and a German-locale Actiwatch Spectrum; more device-format generations behind that same argument are the obvious continuation as manufacturers revise exports. The named milestones (Civil Dawn, then Sunrise) suggest the next substantive release will be another themed one rather than a steady drip.
Alternatives to checkhelper and LightLogR
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 checkhelper or LightLogR.
massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
writeAlizer
Six months of releases and not one of them touched the scoring models
samplr
A cognitive-science sampling package ships once, then goes quiet for eighteen months
stochvol
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all checkhelper alternatives → · See all LightLogR alternatives →
Recent activity from checkhelper and LightLogR
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agocheckhelpercheckhelper 1.0.1 rc1 (CRAN submission candidate)
- 3mo agocheckhelperA static audit_* family for CRAN pre-submission checks ⚡
- 3mo agoLightLogRLYS imports accept any timestamp-prefixed column
- 8mo agoLightLogRCircular time, dataset-wide summaries, versioned device formats ⚡
- 1y agoLightLogRv0.9.2 Sunrise
- 1y agoLightLogRSunrise: cluster detection, metric summaries, new plots
- 1y agoLightLogRv0.5.3 Civil Dawn
- 1y agoLightLogRCitations updated on a merged dev branch
- 2y agocheckhelperTest fixes for roxygen2 changes
- 3y agocheckhelpercheckhelper 0.1.0 - First CRAN Release
Frequently asked questions
What is the difference between checkhelper and LightLogR?
They serve adjacent needs but don't currently overlap on shipped themes. checkhelper 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 checkhelper better than LightLogR?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. checkhelper 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 checkhelper?
Top checkhelper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "checkhelper alternatives" section above for the current picks, or visit /alternatives/checkhelper for the full list with editorial commentary on each.
What are the best alternatives to LightLogR?
Top LightLogR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "LightLogR alternatives" section above for the current picks, or visit /alternatives/lightlogr for the full list with editorial commentary on each.