cIRT
A choice-based IRT model published once in 2019 and kept compiling ever since
Comparison · Analytics
common vs enderecobr
A side-by-side editorial comparison of common and enderecobr — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
common vs enderecobr: at a glance
What is common?
A base-R utility belt that grows one small function at a time, on no particular schedule
common collects small helpers that base R leaves out — data frame labelling and sorting, infix operators for pasting and equality, UTF-8 superscript and subscript lookups, file and directory search, attribute copying between data frames. It has no dependencies to speak of and deliberately removed the one it had. In practice it is the shared substrate for its author's wider package family, and its source.all() function is maintained specifically to cooperate with the logr logging package.
What is enderecobr?
Brazilian address standardisation moves its core to Rust, betting on throughput over pure R
enderecobr standardises Brazilian address fields — street types, neighbourhoods, states, postcodes, house numbers — into consistent forms so records from different registries can be compared. It comes out of the ipeaGIT ecosystem and its API is a family of padronizar_* functions plus one padronizar_enderecos() that runs them together. The 0.5.0 release rewrote those standardisation functions in Rust with a documented speedup.
common vs enderecobr: editorial side-by-side
common
0.0ANALYTICS
A base-R utility belt that grows one small function at a time, on no particular schedule
◆ Current state
common collects small helpers that base R leaves out — data frame labelling and sorting, infix operators for pasting and equality, UTF-8 superscript and subscript lookups, file and directory search, attribute copying between data frames. It has no dependencies to speak of and deliberately removed the one it had. In practice it is the shared substrate for its author's wider package family, and its source.all() function is maintained specifically to cooperate with the logr logging package.
◆ Where it's heading
The pattern is accretion rather than direction: each release adds a couple of utilities and fixes whatever the last batch broke, with gaps of a year or more between them. Function additions cluster around whatever the author's other packages needed at the time — file search, attribute preservation, group-boundary detection, script sourcing. The 2025 release continues exactly this, extending the infix comparison operators from equality alone to the full set of relational tests.
◆ Prediction
Expect more of the same shape — a handful of small helpers whenever a sibling package needs them — with no sign in these entries of a broader API push.
enderecobr
0.0ANALYTICS
Brazilian address standardisation moves its core to Rust, betting on throughput over pure R
◆ Current state
enderecobr standardises Brazilian address fields — street types, neighbourhoods, states, postcodes, house numbers — into consistent forms so records from different registries can be compared. It comes out of the ipeaGIT ecosystem and its API is a family of padronizar_* functions plus one padronizar_enderecos() that runs them together. The 0.5.0 release rewrote those standardisation functions in Rust with a documented speedup.
◆ Where it's heading
Two years of releases were about control and correctness: new formato arguments letting callers choose state names or abbreviations, integers or characters for house numbers, and a run of fixes for numbers mangled by thousands separators. That work settled the semantics. With the behaviour pinned down, the Rust rewrite becomes the natural next move, and the release pairs it with new matching rules for the two messiest fields, neighbourhoods and street names.
◆ Prediction
The rewrite covers the standardisation functions specifically, so the remaining pure-R paths around them are the likely next targets, alongside continued rule additions for street and neighbourhood variants.
Alternatives to common and enderecobr
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 common or enderecobr.
MetaboAnalystR
The R engine behind MetaboAnalyst closes the gap from raw spectra to biological interpretation
fmtr
Rebuilding SAS's formatting layer in R, one format specification at a time
betaselectr
Standardised coefficients for models where standardising everything is wrong — but the feed only links out
SSN2
Stream-network spatial models learning to run on data that no longer fits in memory
BiocManager
Bioconductor's installer, frozen at 1.30.x and tuned almost entirely through environment variables
See all common alternatives → · See all enderecobr alternatives →
Recent activity from common and enderecobr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 7mo agoenderecobrStandardisation functions rewritten in Rust ⚡
- 8mo agocommonFull set of relational infix operators added
- 1y agoenderecobrNamespaced calls no longer error on internal warnings
- 1y agoenderecobrHouse numbers gain output format control, thousands-separator bug fixed
- 1y agoenderecobrStates can be standardised to full names or abbreviations
- 1y agoenderecobrAuthor added to package metadata
- 1y agoenderecobrStreet-type functions added and output columns given a naming convention
- 2y agocommonsource.all() fixed to cooperate with logr
- 2y agocommonsource.all() added for sourcing a directory of scripts
- 2y agocommonchanged() fixed for single-value input
- 2y agocommonchanged() identifies grouping boundaries
- 3y agocommonthis.path() dependency removed
Frequently asked questions
What is the difference between common and enderecobr?
Both compete on the same themes — r-package — within Analytics. common and enderecobr 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 common better than enderecobr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. common and enderecobr 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 common?
Top common alternatives in Analytics are ranked by recent ship velocity. Browse the "common alternatives" section above for the current picks, or visit /alternatives/common for the full list with editorial commentary on each.
What are the best alternatives to enderecobr?
Top enderecobr alternatives in Analytics are ranked by recent ship velocity. Browse the "enderecobr alternatives" section above for the current picks, or visit /alternatives/enderecobr for the full list with editorial commentary on each.