Skip to contents

spicy provides a small set of opinionated, Stata-/SPSS-grade tools for descriptive analysis: frequency tables, cross- tabulations, association measures, variable inspection, and publication-ready summary tables.

API stability

spicy is in active pre-1.0 development. Per the policy documented in NEWS.md and the package roadmap, breaking changes are made deliberately at minor-version bumps and are always announced in NEWS.md. The API surface is partitioned as follows; users planning to embed spicy in production pipelines or downstream packages should rely on the stable surface.

Stable (signature and behaviour preserved across 0.y.z and into 1.0.0; documented changes only):

Stabilising (still maturing; argument names may be tightened before 1.0 with a NEWS.md entry, but no silent behavioural changes):

Internal API (not part of the public surface; can change without notice – avoid calling directly from downstream code):

All errors and warnings emitted by the stable / stabilising surfaces use the documented spicy_error / spicy_warning class hierarchies (see NEWS.md), so downstream code can dispatch on class via tryCatch() / withCallingHandlers() instead of matching message strings.

Author

Maintainer: Amal Tawfik amal.tawfik@hesav.ch (ORCID) (ROR) [copyright holder]

Authors: