At Hyperledger, we are committed to a trust-but-verify security philosophy for our open source projects. We trust the engineering, change management, and risk reduction processes we use in our software supply chain to greatly reduce the risk of security flaws in the finished product. But to verify that is the case, we are organizing outside, independent security audits of the projects as they reach their 1.0 milestone. In addition to code audits, we also conduct regular crypto audits to comply with the US government regulations on the exportation of strong cryptography. Lastly we also run regular license audits to make sure that all of the code in our projects is properly licensed.
Re-auditing Policy
After our projects reach 1.0 status, the policy for when we do another outside audit of a project is based on a few factors. The primary factor is code "churn"–the amount of code that has changed since the last audit. The secondary factor is major architectural changes (e.g. changing cryptography library implementations). When enough code has changed and/or architectural rework has happened, Hyperledger will invest money into having a follow up audit done to once again establish a baseline for project security.