Administrative security review
All software must have an administrative security review before it is made publicly available by any method. This review should ensure that no personal, private, or otherwise sensitive material is included in the repository. Follow the checklist below. All further commits should include an administrative security review to ensure that no sensitive information is included in the git commit history.
Review checklist
Background information for reviewers here
Reviewed by @jzemmels
Please check off boxes as applicable and elaborate in comments below.
Conflict of interest
-
I confirm that I have no COIs with reviewing this work, meaning that there is no relationship with the product or the product's authors or affiliated institutions that could influence or be perceived to influence the outcome of the review (if you are unsure whether you have a conflict, please speak to your supervisor before starting your review).
Adherence to Fundamental Science Practices
-
I confirm that I read and will adhere to the Federal Source Code Policy for Scientific Software and relevant federal guidelines for approved software release as outlined in SM502.1 and SM502.4.
Security Review
-
No proprietary code is included -
No Personally Identifiable Information (PII) is included -
No other sensitive information such as data base passwords are included
Review Comments
- Add free text comments here.
Reviewer checklist source statement
This checklist was developed by the Volcano Science Center (link). It combines elements of the rOpenSci review guidelines and the Journal of Open Source Science (JOSS) review checklist: it has been modified for use with USGS software releases.