incident.io
Nexus does the diagnosis; the agent is now reaching into the status page too.
A side-by-side editorial comparison of Fiscal and tealeaves — release velocity, themes, recent moves, and the top alternatives to consider.
UK income tax calculations reach CRAN, then go quiet behind pointer-only release notes.
Fiscal computes UK income tax. It reached its 1.0.0 milestone in March 2026 and shipped two patch releases in the fortnight after, then stopped. The GitHub release bodies carry no changelog of their own: each one points at the NEWS file and the CRAN page, so the feed shows cadence but not content.
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.
Fiscal computes UK income tax. It reached its 1.0.0 milestone in March 2026 and shipped two patch releases in the fortnight after, then stopped. The GitHub release bodies carry no changelog of their own: each one points at the NEWS file and the CRAN page, so the feed shows cadence but not content.
Three releases in a fifteen-day window reads as post-publication cleanup rather than a development push, which is the normal shape after a first CRAN acceptance. Because every body is the same boilerplate, direction has to be read from the tags alone, and the tags say only that two patches followed the 1.0.0 line.
The most likely next release is an annual one tracking a new UK tax year's rates and thresholds. The release notes as published give no evidence for anything beyond that.
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.
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.
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.
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 Fiscal or tealeaves.
Nexus does the diagnosis; the agent is now reaching into the status page too.
Warp turned its quarter of software-factory essays into infrastructure you can buy.
Okta's developer blog is a Cross App Access campaign, now diluted by advocacy-team storytelling.
A credential platform assembled two or three pull requests at a time, never a headline
Search without knowing the field — SigNoz keeps lowering the cost of not knowing your schema
A NOAA Fisheries colour palette that ships when the branding guide changes
See all Fiscal alternatives → · See all tealeaves alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fiscal 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fiscal 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.
Top Fiscal alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Fiscal alternatives" section above for the current picks, or visit /alternatives/fiscal for the full list with editorial commentary on each.
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.