Workshop: evaluate pkg quality with the {riskassessment} application
📞 Community Meetings
Sign up
- Follow the R Consortium’s Linkedin
- ✉ Join our mailing list! (pharmaR.org > Contact Us)
Latest Features
Two tools: what do they do
is a framework to quantify an R package’s “risk” by assessing several meaningful metrics designed to evaluate package development best practices, code documentation, community engagement, and development sustainability.
is a full-fledged R package containing a shiny front-end that augments the utility of {riskmetric}. The application’s goal is to provide a central hub for an organization to review and assess the risk of R packages, providing handy tools and guide rails along the way.
Quantify risk programmatically
Sometimes “quality” is measurable! Software dev best practices dictate an R-package should have:
- A license
- Source code available for browsing
- An easy to contact maintainer
- A place to report bugs
- Evidence that new bugs are being addressed
- Complete Function documentation
- Adequate test coverage
- Community usage
18 total assessments (to date)!
Why create a Shiny app?
Main goal: complement GxP “package inclusion requests” with data.
Why create a Shiny app?
Main goal: complement GxP “package inclusion requests” with data.
Why create a Shiny app?
Main goal: complement GxP “package inclusion requests” with data.
Why create a Shiny app?
Main goal: complement GxP “package inclusion requests” with data.
- Shifts responsibility of assessing package risk to the person(s) requesting it
Why create a Shiny app?
Main goal: complement GxP “package inclusion requests” with data.
- Shifts responsibility of assessing package risk to the person(s) requesting it
- Leverage the app’s risk-based “decision triage” (based on org-defined rules) to output a risk summary report
Why create a Shiny app?
Main goal: complement GxP “package inclusion requests” with data.
- Shifts responsibility of assessing package risk to the person(s) requesting it
- Leverage the app’s risk-based “decision triage” (based on org-defined rules) to output a risk summary report
- Changes communication from “Can we add this?” to a informed “We can add this.”
Why create a Shiny app? (cont’d)
Bonus / Secondary Perks:
- Provide a platform for package exploration without the need to write any custom
{riskmetric} - Run
{riskmetric}on the same machine with the same environment – creating a central hub for reproducibility - Maintain consistent, org-specific settings/options when producing risk outputs
- Manage who’s involved in the review process via user authentication & role management
- Facilitate and store user summaries & communication, on packages and/or metrics
I want it
Start with {riskassessment}
Submit {riskassessment} Report(s)
![]()
R Consortium Affiliation
Community Grants & Sponsorships
Over USD $1.4 Million
Organizing Large Scale Collaborative Projects
R Validation Hub, R-Ladies
Co-Host Multidisciplinary Data Science Forums
Stanford Data Institute
Direct Support for Key R Events
R/Medicine, R/Pharma, useR!, LatinR, and more
