Risk thresholds & metric weights

[AARON-CLARK]

This a forum to track ideas and continue discussion initiated at the R Validation Hub's Community meeting on 2023/6/27! Get a conversation started below!

[AARON-CLARK]

Risk Scores

Do you (or your org) care about {riskmetric} scores? Yes or No, and why?

[AARON-CLARK]

Risk Score Thresholds

How high is too high? Enter a number between 0 & 1. How do you make this determination?

[AARON-CLARK]

Package Weights!

• news_current: News file has an entry for the current version of the package.
  
• has_vignettes: package contains vignettes.
  
• size_codebase: a logistic rating of the number of lines of code in the package.
  
• has_bug_reports_url: package links to a location to file bug reports.
  
• bugs_status: fraction of the last 30 bugs which have been closed.
  
• license: the package ships with an acceptable license.
  
• export_help: fraction of exported objects that are documented.
  
• reverse_dependencies: (log10) number of packages that depend on this package.
  
• downloads_1yr: logistic rating of the number of package downloads in the past year.
  
• dependencies: number of package dependencies.
  
• has_website: package has an accompanying website.
  
• r_cmd_check: weighted sum of errors/warnings/notes from R CMD Check.
  
• remote_checks: weighted sum of OS flavor R CMD check results.
  
• has_maintainer: package has a maintainer.
  
• exported_namespace: fraction of exported objects that are documented.
  
• has_news: package has a NEWS file.
  
• has_source_control: package has an associated version-controlled repository.
  
• covr_coverage: fraction of lines of code which are covered by a unit test.
  

Which metrics would you up-weight or down-weight to calculate a risk score that reflects your priorities?