← Back to home
Comparison · Analytics

lavaanExtra vs ojoregex

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

Shared themes:r-package

lavaanExtra vs ojoregex: at a glance

FeaturelavaanExtraojoregex
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesr-package, structural-equation-modeling, lavaan, apa-reportingcriminal-justice, court-data, r-package, text-classification
Last editorial update53m ago6h ago
WebsiteVisit →Visit →

What is lavaanExtra?

SEM reporting helpers converging on APA output, one CRAN resubmission at a time.

lavaanExtra provides shorthand syntax and formatted output around lavaan structural equation models - write_lavaan() to build model strings, and nice_* functions for fit tables, plots, and modification indices. Three of the six visible releases exist only to satisfy CRAN resubmission: a unicode problem, a dependency version check, tests running without suggested packages. The substance sits in 0.1.5, 0.1.8, and 0.1.9.

Read the full lavaanExtra trajectory →

What is ojoregex?

Oklahoma's court-data nonprofit maintains the regex layer that turns charge text into categories.

ojoregex is Open Justice Oklahoma's pattern library for classifying criminal charge descriptions from court records — the unglamorous translation layer between free-text charge fields and analysable categories. Its entire release history reached this feed as four tags published within three minutes, so the feed order reflects a backfill rather than a shipping cadence. Release notes are merge references rather than descriptions, which limits how much can be read from the changelog alone.

Read the full ojoregex trajectory →

lavaanExtra vs ojoregex: editorial side-by-side

L
lavaanExtra
ANALYTICS
0.0

SEM reporting helpers converging on APA output, one CRAN resubmission at a time.

◆ Current state

lavaanExtra provides shorthand syntax and formatted output around lavaan structural equation models - write_lavaan() to build model strings, and nice_* functions for fit tables, plots, and modification indices. Three of the six visible releases exist only to satisfy CRAN resubmission: a unicode problem, a dependency version check, tests running without suggested packages. The substance sits in 0.1.5, 0.1.8, and 0.1.9.

◆ Where it's heading

The package generalises its own vocabulary as it goes: lavaan_ind() became lavaan_defined() once it turned out to extract any user-defined parameter, and lavaan_cov() was split so lavaan_cor() covers actual correlations. Methodological positions are taken alongside the API - dropping the estimate argument from lavaan_reg() to force reporting both standardized and unstandardized values, and updating the RMSEA benchmark to Schreiber (2017). Rémi Thériault maintains it next to rempsyc, which formats output to match. Note that 0.1.5 restates the whole 0.1.4.x development series in one body.

◆ Prediction

The pattern points to another nice_* helper aimed at a reporting step that currently needs hand formatting, arriving with the usual CRAN resubmission behind it.

O
ojoregex
ANALYTICS
0.0

Oklahoma's court-data nonprofit maintains the regex layer that turns charge text into categories.

◆ Current state

ojoregex is Open Justice Oklahoma's pattern library for classifying criminal charge descriptions from court records — the unglamorous translation layer between free-text charge fields and analysable categories. Its entire release history reached this feed as four tags published within three minutes, so the feed order reflects a backfill rather than a shipping cadence. Release notes are merge references rather than descriptions, which limits how much can be read from the changelog alone.

◆ Where it's heading

What the notes do show is a package alternating between domain corrections and R tooling upkeep: a fix to property-crime matching in one release, dplyr select semantics in the next. That is the expected shape for a regex catalogue — accuracy work arrives as individual charge types get miscategorised in real analyses, and the rest is keeping the package installable against a moving tidyverse. Contributions come from a small internal team, and the vignette work referenced in the earliest tag suggests the pattern list doubles as documentation for analysts.

◆ Prediction

The visible pattern is incremental match fixes as charge types surface in use; the release notes carry too little detail to predict anything beyond that without reading the underlying pull requests.

Alternatives to lavaanExtra and ojoregex

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 lavaanExtra or ojoregex.

See all lavaanExtra alternatives → · See all ojoregex alternatives →

Recent activity from lavaanExtra and ojoregex

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

  1. 1mo agoojoregexPatch for dplyr select semantics
  2. 1mo agoojoregexojoregex v0.10.0
  3. 1mo agoojoregexNamespace prefixes fixed, plus a property-crime match bug
  4. 1mo agoojoregexFirst tagged release, carrying the whole development history
  5. 2y agolavaanExtraCRAN resubmission for a unicode problem
  6. 2y agolavaanExtralavaan_ind renamed to lavaan_defined; thresholds supported
  7. 2y agolavaanExtranice_modindices flags redundant items
  8. 3y agolavaanExtraSuggested dependency versions checked correctly
  9. 3y agolavaanExtraTests run without suggested dependencies
  10. 3y agolavaanExtraFit benchmarks updated and correlations split from covariances

Frequently asked questions

What is the difference between lavaanExtra and ojoregex?

Both compete on the same themes — r-package — within Analytics. lavaanExtra and ojoregex 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 lavaanExtra better than ojoregex?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. lavaanExtra and ojoregex 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 lavaanExtra?

Top lavaanExtra alternatives in Analytics are ranked by recent ship velocity. Browse the "lavaanExtra alternatives" section above for the current picks, or visit /alternatives/lavaanextra for the full list with editorial commentary on each.

What are the best alternatives to ojoregex?

Top ojoregex alternatives in Analytics are ranked by recent ship velocity. Browse the "ojoregex alternatives" section above for the current picks, or visit /alternatives/ojoregex for the full list with editorial commentary on each.