Announcing the R Validation Hub Early Adopter Guide

| October 14, 2026

The R Validation Hub is looking for early adopters! We have published an Early Adopter Guide to help organizations pilot our new set of tools for validating R packages in regulated environments, and we want your feedback on them.

Why early adoption?

Early adopters play a dual role: implementers, piloting the tools in their own environment, and contributors, sharing insights that shape the tools and community best practices. In return, adopters get direct communication with the maintainers, early access to updates, influence on the roadmap, and (if they choose) recognition in community reports and presentations.

You don’t need to be an expert R developer. The guide is written for the platform engineers, statisticians, data scientists, and IT teams who typically implement validation workflows.

The tools

The tools are designed to work together as a pipeline:

  • {val.meter}: measure characteristics of packages and leave the decision about acceptable risk to you. It is the successor to {riskmetric}.
  • val.repo: a curated, CRAN-like repository of R packages with additional metadata and validation reports. Explore the public example at https://pharmar.github.io/val.repo/.
  • {val.report}: generate validation reports for packages.
  • {val.criterion}: apply default or bespoke filtering criteria to metrics, and visualize them as decision trees.
  • val.dashboard: evolving support intended to provide a Shiny app for reviewing metrics, applying criteria, and discussing risk, based on the experience of {riskassessment}.
  • {val.setup}: evolving support intended to bring the tools together in a single GitHub Actions workflow that produces the outputs needed to qualify R packages for a GxP system.

Choose your starting point

The guide describes four workflows, so you can start at the level that fits your governance model and maturity:

  1. Empower analysts to make validation decisions with package metrics.
  2. Curate packages using a validation policy.
  3. Impose a validation policy for an enterprise system.
  4. Generate an internal validated repository or image with reports and repeatable automation.

You can begin with lightweight workflows and evolve toward centralized governance and automated validation over time.

Get involved

We look forward to learning with you!