Citing theoryforge
If you use the R package in your work, please cite it:
Bernabeu, P. (2026). theoryforge: Systematic theory development (R package version 0.6.0). Comprehensive R Archive Network (CRAN). https://doi.org/10.32614/CRAN.package.theoryforge
@Manual{theoryforge,
title = {{theoryforge}: Systematic theory development},
author = {Pablo Bernabeu},
year = {2026},
publisher = {Comprehensive R Archive Network (CRAN)},
note = {R package version 0.6.0},
doi = {10.32614/CRAN.package.theoryforge},
url = {https://CRAN.R-project.org/package=theoryforge},
}In R, the same entry is available with
citation("theoryforge"). The package installs from CRAN
with install.packages("theoryforge"), and the development
version with
remotes::install_github("pablobernabeu/theoryforge", subdir = "r/theoryforge").
The developer
theoryforge is developed and maintained 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, and research methods and open science, with hands-on experience in behavioural and EEG experiments, corpus analysis, computational modelling and statistics. He develops open, reproducible research software in R and Python, and is a Fellow of the Software Sustainability Institute. His ORCID record lists his other work.
This R package has a feature-parity twin written in Python. Its documentation lives at the theoryforge (Python) site, keeping a theory development workflow legible across both languages.
Licence
theoryforge is released under the MIT licence, a permissive licence that allows use, modification and redistribution provided the copyright and licence notices are kept. The full text is reproduced on this site’s licence page.
Versioning and archival
CRAN assigned the package the DOI https://doi.org/10.32614/CRAN.package.theoryforge on publication. It names the R package across all its versions, so the version in the citation identifies the release used. Releases of the repository, which carry the Python twin as well, are tagged on GitHub and archived on Zenodo, where the concept DOI, https://doi.org/10.5281/zenodo.21229964, resolves to the latest archived release and each release has a DOI of its own. The changelog records what changed in each release.
Contributing and support
Bugs and feature requests are best reported on the GitHub issues page, and the contributing guide explains how to set up a development environment and propose a change. Because the OSF deposit adapter takes a personal access token, never paste that token, or any other secret, into an issue. Replace it with a placeholder.