ANALYTICS
A tables-listings-graphs package that reached CRAN and then went quiet.
Alternatives · analytics tools
forcis alternatives
The best forcis alternatives in analytics tools, ranked by Sparkpulse's velocity_score.
Updated Aug 14, 2026
Looking for the best alternatives to forcis? Sparkpulse tracks and ranks 12 alternatives in analytics tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, forcis shipped 0 meaningful updates in the last 30 days and carries a velocity score of 0.0 out of 10 in 2026. The alternatives below are ranked the same way, so you're comparing real release momentum, not marketing claims.
About forcis
A foraminifera data-access package whose entire release history is the rOpenSci review process.
forcis provides R access to the FORCIS database of planktonic foraminifera occurrences. All three releases in the window are review milestones rather than feature work: first stable release, the release answering rOpenSci reviewer comments, and a post-CRAN-review polish. Release notes point at NEWS.md rather than enumerating changes.
Velocity 0.0 · Last update 59m ago
Top 12 alternatives to forcis
Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.
ANALYTICS
Tplyr made clinical summary tables explain where every number came from.
ANALYTICS
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
ANALYTICS
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
ANALYTICS
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
ANALYTICS
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
ANALYTICS
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
ANALYTICS
A TIFF reader for scientific imaging that spent its recent releases shedding weight and fixing memory bugs.
ANALYTICS
tern is migrating its entire analysis-function catalogue off make_afun(), one release at a time.
ANALYTICS
A reference posterior database that hit 1.0 with a paper, and is now graded on the statistics it ships.
ANALYTICS
Markdown round-tripping through XML, where every release is another thing it learned not to mangle.
ANALYTICS
A Qualtrics data-cleaning package that has been in maintenance mode since its CRAN acceptance.
forcis vs alternatives — shipping velocity at a glance
Velocity score (0–10) and meaningful releases shipped in the last 30 days, from official changelogs. Higher = shipping faster.
| Product | Velocity | Sparks · 30d | Focus areas | Latest release |
|---|---|---|---|---|
| forcis (baseline) | 0.0 | 0 | data-accessr-packageropensci | — |
| tidytlg | 0.0 | 0 | clinical-trialstablesr-package | — |
| Tplyr | 0.0 | 0 | clinical-trialstablestraceability | 1.0.0 introduces the traceability metadata framework |
| rlistings | 0.0 | 0 | clinical-trialslistingspagination | — |
| hoardr | 0.0 | 0 | cachingr-packageropensci | — |
| gigs | 0.0 | 0 | growth-standardsneonatal-healthr-package | Conversion API rewritten around data frames and classify_growth() |
| riem | 0.0 | 0 | weather-dataapi-clientr-package | — |
| datasetjson | 0.0 | 0 | clinical-datacdiscjson | Dataset-JSON 1.1.0 support with a redesigned object model |
| ijtiff | 0.0 | 0 | imagingtiffr-package | — |
| tern | 0.0 | 0 | clinical-trialstablesr-package | Two dozen more analysis functions drop make_afun() |
| posteriordb | 0.0 | 0 | bayesianbenchmarkingreference-data | — |
| tinkr | 0.0 | 0 | markdownxmlr-package | First release: the extensible yarn R6 class |
| excluder | 0.0 | 0 | survey-datadata-cleaningr-package | — |
The 12 best forcis alternatives, in depth
1. tidytlg · velocity 0.0
A tables-listings-graphs package that reached CRAN and then went quiet.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where forcis leans on data access, r package and ropensci, tidytlg focuses on clinical trials, tables and r package.
tidytlg and forcis have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
2. Tplyr · velocity 0.0
Tplyr made clinical summary tables explain where every number came from.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “1.0.0 introduces the traceability metadata framework”.
Where forcis leans on data access, r package and ropensci, Tplyr focuses on clinical trials, tables and traceability.
Tplyr and forcis have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
3. rlistings · velocity 0.0
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where forcis leans on data access, r package and ropensci, rlistings focuses on clinical trials, listings and pagination.
rlistings and forcis have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
4. hoardr · velocity 0.0
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where forcis leans on data access, r package and ropensci, hoardr focuses on caching, r package and ropensci.
hoardr and forcis have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
5. gigs · velocity 0.0
Gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Conversion API rewritten around data frames and classify_growth()”.
Where forcis leans on data access, r package and ropensci, gigs focuses on growth standards, neonatal health and r package.
gigs and forcis have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
6. riem · velocity 0.0
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where forcis leans on data access, r package and ropensci, riem focuses on weather data, api client and r package.
riem and forcis have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
7. datasetjson · velocity 0.0
Datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Dataset-JSON 1.1.0 support with a redesigned object model”.
Where forcis leans on data access, r package and ropensci, datasetjson focuses on clinical data, cdisc and json.
datasetjson and forcis have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full datasetjson trajectory → · Compare forcis vs datasetjson →
8. ijtiff · velocity 0.0
A TIFF reader for scientific imaging that spent its recent releases shedding weight and fixing memory bugs.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where forcis leans on data access, r package and ropensci, ijtiff focuses on imaging, tiff and r package.
ijtiff and forcis have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
9. tern · velocity 0.0
Tern is migrating its entire analysis-function catalogue off make_afun(), one release at a time.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Two dozen more analysis functions drop make_afun()”.
Where forcis leans on data access, r package and ropensci, tern focuses on clinical trials, tables and r package.
tern and forcis have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
10. posteriordb · velocity 0.0
A reference posterior database that hit 1.0 with a paper, and is now graded on the statistics it ships.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where forcis leans on data access, r package and ropensci, posteriordb focuses on bayesian, benchmarking and reference data.
posteriordb and forcis have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full posteriordb trajectory → · Compare forcis vs posteriordb →
11. tinkr · velocity 0.0
Markdown round-tripping through XML, where every release is another thing it learned not to mangle.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “First release: the extensible yarn R6 class”.
Where forcis leans on data access, r package and ropensci, tinkr focuses on markdown, xml and r package.
tinkr and forcis have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
12. excluder · velocity 0.0
A Qualtrics data-cleaning package that has been in maintenance mode since its CRAN acceptance.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where forcis leans on data access, r package and ropensci, excluder focuses on survey data, data cleaning and r package.
excluder and forcis have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Frequently asked questions
What are the best alternatives to forcis?
The top forcis alternatives we currently track in analytics tools are tidytlg, Tplyr, rlistings, hoardr, gigs, ranked by recent ship velocity.
How is this list of forcis alternatives ranked?
Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.
Can I compare forcis directly with one of these alternatives?
Yes — every card has a "Compare with forcis" link to a side-by-side /compare page.