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.

metalabr: Access MetaLab Community-Augmented Meta-Analysis Data

Read released, versioned data from MetaLab (<https://metalab.stanford.edu>), a database of community-augmented meta-analyses of language acquisition and cognitive development; validate candidate datasets against the MetaLab field specification; compute standardized effect sizes; and draw the standard MetaLab visualizations (scatter, violin, forest, and funnel plots) backed by multilevel random-effects models.

Version: 1.0.0
Imports: assertthat, dplyr, ggplot2, Hmisc, httr, jsonlite, magrittr, metafor, purrr, rlang, stringr, tibble, yaml
Suggests: knitr, readr, redivis, rmarkdown, testthat (≥ 3.0.0)
Published: 2026-10-08
DOI: 10.32614/CRAN.package.metalabr
Author: Erik Iverson [aut], Sara El-Shawa [aut], Michael C. Frank ORCID iD [aut, cre], MetaLab contributors [cph]
Maintainer: Michael C. Frank <mcfrank at stanford.edu>
BugReports: https://github.com/langcog/metalabr/issues
License: MIT + file LICENSE
URL: https://github.com/langcog/metalabr, https://metalab.stanford.edu
NeedsCompilation: no
Additional_repositories: https://langcog.r-universe.dev
Materials: README, NEWS
CRAN checks: metalabr results

Documentation:

Reference manual: metalabr.html , metalabr.pdf
Vignettes: Accessing MetaLab data (source, R code)

Downloads:

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

Linking:

Please use the canonical form https://CRAN.R-project.org/package=metalabr 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.