The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

semFromKeys: Run 'lavaan' Models from Keys Lists

Specifying 'lavaan' models manually can be time consuming when multiple similar models are required. The 'semFromKeys' package streamlines the process of running 'lavaan' models by generating model code from simple keys lists and running entire collections of models at once. The package was inspired by the process used in the code for Bainbridge, T. F., Ludeke, S. G., & Smillie, L. D. (2022) <doi:10.1037/pspp0000395>. The package also optionally checks that identical models have not been run on the same data, which saves time when code needs to be run again.

Version: 0.2.2
Depends: R (≥ 3.6.0)
Imports: stringr, lavaan, openssl, withr, tools
Suggests: testthat (≥ 3.0.0), here, rstudioapi
Published: 2026-07-24
DOI: 10.32614/CRAN.package.semFromKeys
Author: Timothy F. Bainbridge [aut, cre, cph]
Maintainer: Timothy F. Bainbridge <tfbainbridge at gmail.com>
BugReports: https://github.com/timbainbridge/semFromKeys/issues
License: GPL (≥ 3)
URL: https://github.com/timbainbridge/semFromKeys
NeedsCompilation: no
Citation: semFromKeys citation info
Materials: README, NEWS
CRAN checks: semFromKeys results [issues need fixing before 2026-08-21]

Documentation:

Reference manual: semFromKeys.html , semFromKeys.pdf

Downloads:

Package source: semFromKeys_0.2.2.tar.gz
Windows binaries: r-devel: semFromKeys_0.2.2.zip, r-release: not available, r-oldrel: semFromKeys_0.2.2.zip
macOS binaries: r-release (arm64): semFromKeys_0.2.2.tgz, r-oldrel (arm64): semFromKeys_0.2.2.tgz, r-release (x86_64): semFromKeys_0.2.2.tgz, r-oldrel (x86_64): semFromKeys_0.2.2.tgz

Linking:

Please use the canonical form https://CRAN.R-project.org/package=semFromKeys to link to this page.

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.