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 onemap — 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 genetic-mapping mainstay that now points new users toward MAPpoly at load time
OneMap constructs genetic linkage maps for experimental crosses, and its 3.x line turned it into a hub in a wider mapping toolchain: export functions for VIEWpoly and QTLpoly, summary and interactive ordering functions adapted from MAPpoly, and retention of reference and alternative allele information from imported VCFs. The most recent release, 3.2.0 in January 2025, adds an announcement about MAPpoly to the README and the package load message, fixes a subscript-out-of-bounds warning in rf_2pts and refreshes vignettes and tests.
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.
OneMap constructs genetic linkage maps for experimental crosses, and its 3.x line turned it into a hub in a wider mapping toolchain: export functions for VIEWpoly and QTLpoly, summary and interactive ordering functions adapted from MAPpoly, and retention of reference and alternative allele information from imported VCFs. The most recent release, 3.2.0 in January 2025, adds an announcement about MAPpoly to the README and the package load message, fixes a subscript-out-of-bounds warning in rf_2pts and refreshes vignettes and tests.
Versions 3.0.0 and 3.1.0 were driven by a benchmarking preprint on genotyping-by-sequencing best practice, and their content follows directly: marker filtering from two-point estimates, memory reduction after filtering, and optimisation of find_bins and map_avoid_unlinked. What has happened since is signposting rather than capability — a package that spent two releases integrating with MAPpoly now tells users about it every time it loads. The pre-3.0 tags are backfilled, with versions 2.3 through 2.7 sharing a single August 2021 timestamp, so their order carries no information.
The load-message announcement suggests attention is flowing toward the MAPpoly side of the toolchain; expect maintenance and compatibility releases here rather than new mapping algorithms.
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 onemap.
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 leaf-temperature model that finished its job in 2020 and has stayed finished
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
See all Fiscal alternatives → · See all onemap 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 onemap 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 onemap 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 onemap alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "onemap alternatives" section above for the current picks, or visit /alternatives/onemap for the full list with editorial commentary on each.