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.4.0). https://doi.org/10.5281/zenodo.21229964
@Manual{theoryforge,
title = {theoryforge: Systematic theory development},
author = {Pablo Bernabeu},
year = {2026},
note = {R package version 0.4.0},
doi = {10.5281/zenodo.21229964},
url = {https://doi.org/10.5281/zenodo.21229964},
}You can download the BibTeX
entry. In R, the same entry is available with
citation("theoryforge"). Once on CRAN, the package will
install with install.packages("theoryforge"); until then,
use
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
Releases are tagged on GitHub and archived on Zenodo. The concept DOI, 10.5281/zenodo.21229964, always resolves to the latest version, so a citation stays current without naming a version. 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.