The Sanofi R Validation team is currently creating a number of cutting edge GitHub processes to employ the risk.assessr package to help Sanofi effectively manage risks associated with internal, third-party and open-source packages.  

The first process is a database to store the risk metric data (RCMD check, test coverage, documentation metrics, traceability matrix), create Sanofi risk thresholds, and generate documentation for package acceptance/rejection for the team to make a decision about a target package. The process also populates the documentation with any metrics that do not pass the Sanofi criteria. 

Next is a GitHub CICD process to run risk.assessr on an individual target package for a specific package evaluation and store that data in the DB. The final process is a GitHub CICD process to run the risk.assessr functionality to process renv.lock files that contain a target package and its dependencies and store the data collected in the DB.  
Hugo Bottois
Sanofi
risk.assessr:  extending its use in the package validation process
The Sanofi R Validation team is currently creating a number of cutting edge GitHub processes to employ the risk.assessr package to help Sanofi effectively manage risks associated with internal, third-party and open-source packages.    The first process is a database to store the risk metric data (RCMD check, test coverage, documentation metrics, traceability matrix), create Sanofi risk thresholds, and generate documentation for package acceptance/rejection for the team to make a decision about a target package. The process also populates the documentation with any metrics that do not pass the Sanofi criteria.   Next is a GitHub CICD process to run risk.assessr on an individual target package for a specific package evaluation and store that data in the DB. The final process is a GitHub CICD process to run the risk.assessr functionality to process renv.lock files that contain a target package and its dependencies and store the data collected in the DB.  