incident.io
Nexus does the diagnosis; the agent is now reaching into the status page too.
Comparison · Infra & APIs
hicp vs tealeaves
A side-by-side editorial comparison of hicp and tealeaves — release velocity, themes, recent moves, and the top alternatives to consider.
hicp vs tealeaves: at a glance
What is hicp?
Eurostat's inflation package moved its whole taxonomy to ECOICOP 2 and broke the old one on purpose.
hicp downloads and computes the Harmonised Index of Consumer Prices, and it is maintained inside Eurostat rather than around it. Version 1.1.0 switches the package default to ECOICOP version 2 for HICP, converts the spec.aggs and countries datasets into functions that answer per COICOP version, and drops the bundle-code machinery that only the older classification needs.
What is tealeaves?
A leaf-temperature model that finished its job in 2020 and has stayed finished
tealeaves solves for leaf temperature from an energy balance, using explicit units to keep parameters consistent and modelling lower and upper leaf surfaces separately so sensible and latent heat loss are computed for each. The package reached its current form in 2020 across versions 1.0.2 to 1.0.5, which added direct or functional sky temperature, dplyr 1.0.0 compatibility, and fixes to a parameter-crossing bug that the new sky temperature function had introduced. The only release since, v1.0.6 in July 2022, corrects a name in the citation file, stops parallel evaluation in a vignette and fixes README links.
hicp vs tealeaves: editorial side-by-side
hicp
0.0INFRA · APIS
Eurostat's inflation package moved its whole taxonomy to ECOICOP 2 and broke the old one on purpose.
◆ Current state
hicp downloads and computes the Harmonised Index of Consumer Prices, and it is maintained inside Eurostat rather than around it. Version 1.1.0 switches the package default to ECOICOP version 2 for HICP, converts the spec.aggs and countries datasets into functions that answer per COICOP version, and drops the bundle-code machinery that only the older classification needs.
◆ Where it's heading
Two breaking releases in seven months, each clearing a different kind of debt. 1.0.0 settled the API: consistent download-function names, aggregation split into tree-following and user-defined halves, a settings object threaded through everything. 1.1.0 then spent that stability on the classification migration. Datasets keep turning into functions, which is the tell that the package expects to serve several COICOP versions at once rather than one at a time.
◆ Prediction
The ecoicop1 compatibility path is defined but no longer the default, so the next question is how long it stays. Expect further helpers in the is.* family and continued movement of static data behind version-aware functions.
tealeaves
0.0INFRA · APIS
A leaf-temperature model that finished its job in 2020 and has stayed finished
◆ Current state
tealeaves solves for leaf temperature from an energy balance, using explicit units to keep parameters consistent and modelling lower and upper leaf surfaces separately so sensible and latent heat loss are computed for each. The package reached its current form in 2020 across versions 1.0.2 to 1.0.5, which added direct or functional sky temperature, dplyr 1.0.0 compatibility, and fixes to a parameter-crossing bug that the new sky temperature function had introduced. The only release since, v1.0.6 in July 2022, corrects a name in the citation file, stops parallel evaluation in a vignette and fixes README links.
◆ Where it's heading
This is finished scientific software. The arc runs from a 1.0.0 that already described the full model, through a usability decision in 1.0.1 to accept unitless values and assign units rather than demand them, to a 2020 cluster of compatibility and correctness work around publication. Nothing since has touched the model, and the 2022 release is pure paperwork. Its most instructive entry remains 1.0.5, where a new feature silently produced incorrect parameter crossing and the fix arrived with tests to pin the behaviour.
◆ Prediction
Expect nothing unless a dependency or CRAN check forces a release; on this record any such release will be documentation and packaging rather than a change to the energy balance.
Alternatives to hicp and tealeaves
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 hicp or tealeaves.
Warp
Warp turned its quarter of software-factory essays into infrastructure you can buy.
Okta
Okta's developer blog is a Cross App Access campaign, now diluted by advocacy-team storytelling.
Infisical
A credential platform assembled two or three pull requests at a time, never a headline
SigNoz
Search without knowing the field — SigNoz keeps lowering the cost of not knowing your schema
nmfspalette
A NOAA Fisheries colour palette that ships when the branding guide changes
See all hicp alternatives → · See all tealeaves alternatives →
Recent activity from hicp and tealeaves
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6mo agohicpDefault classification moves to ECOICOP 2, retiring bundle codes ⚡
- 6mo agohicpDownload functions accept all defaults via dots
- 1y agohicp1.0 splits aggregation into tree-following and user-defined halves ⚡
- 2y agohicpVignette build fix for one CRAN check flavour
- 2y agohicpGlobal options and a settings argument make COICOP version selectable
- 2y agohicpElementary index weight checks and chain() NA handling fixed
- 4y agotealeavesCitation file, vignette and README fixes
- 6y agotealeavesParameter-crossing bug fixed with tests; coverage added
- 6y agotealeavesFix for custom sky temperature function being overwritten
- 6y agotealeavesSky temperature as value or function; dplyr 1.0.0 compatibility
- 7y agotealeavesUnitless parameter values now accepted and assigned units
- 7y agotealeavesFirst release: leaf energy balance with per-surface conductances
Frequently asked questions
What is the difference between hicp and tealeaves?
They serve adjacent needs but don't currently overlap on shipped themes. hicp and tealeaves 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 hicp better than tealeaves?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. hicp and tealeaves 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to hicp?
Top hicp alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "hicp alternatives" section above for the current picks, or visit /alternatives/hicp for the full list with editorial commentary on each.
What are the best alternatives to tealeaves?
Top tealeaves alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "tealeaves alternatives" section above for the current picks, or visit /alternatives/tealeaves for the full list with editorial commentary on each.