Citing depictr
If you use depictr in published work, please cite it.
Bernabeu, P. (2026). depictr: A unified toolkit for visualising statistical models and data. R package version 0.3.0. Comprehensive R Archive Network (CRAN). https://doi.org/10.32614/CRAN.package.depictr
@Manual{depictr,
title = {{depictr}: A unified toolkit for visualising statistical models and data},
author = {Pablo Bernabeu},
year = {2026},
publisher = {Comprehensive R Archive Network (CRAN)},
note = {R package version 0.3.0},
doi = {10.32614/CRAN.package.depictr},
url = {https://CRAN.R-project.org/package=depictr},
}R users can also retrieve this citation directly with
citation("depictr").
The developer
depictr is developed by Pablo Bernabeu, a researcher in the Department of Education at the University of Oxford. His work spans cognitive psychology and neuroscience, linguistics, education and digital technologies, drawing on a range of methods that include behavioural and EEG experiments, corpus analysis and computational modelling. He is a Fellow of the Software Sustainability Institute (2020), recognised for his work on R-based tools for data presentation, and holds a PhD in Psychology from Lancaster University.
More about his work is on his website, on GitHub and via ORCID 0000-0003-1083-2460.
A sibling Python package, available on PyPI, shares the same design.
Licence
depictr is released under the MIT licence, a short permissive licence that allows use, modification and redistribution in both open and closed projects, provided the copyright notice is retained. The full text is on the site’s licence page.
Versioning and archival
CRAN assigned the package the DOI https://doi.org/10.32614/CRAN.package.depictr on publication. It names the package across all its versions, so the version in the citation identifies the release used. Releases are also tagged on GitHub and archived on Zenodo, where the concept DOI https://doi.org/10.5281/zenodo.21266308 resolves to the latest archived release and each release has a DOI of its own. What changed in each release is recorded in the changelog.
Contributing and support
Bugs and feature requests are best reported on the GitHub issues page, ideally with a small reproducible example. The contributing guide explains how to set up for development and what to check before opening a pull request.