Merge pull request #315 from crytic/code-maturity

Code maturity

Author: montyly

README.md

@@ -7,6 +7,7 @@ Brought to you by [Trail of Bits](https://www.trailofbits.com/), this repository
 **Table of Contents:**
 
 - [Development Guidelines](./development-guidelines)
+  - [Code Maturity](./development-guidelines/code_maturity.md): Criteria for developers and security engineers to use when evaluating a codebase’s maturity
   - [High-Level Best Practices](./development-guidelines/guidelines.md): Best practices for all smart contracts
   - [Incident Response Recommendations](./development-guidelines/incident_response.md): Guidelines for creating an incident response plan
   - [Secure Development Workflow](./development-guidelines/workflow.md): A high-level process to follow during code development

SUMMARY.md

@@ -3,6 +3,7 @@
 [Introduction](./README.md)
 
 - [Development Guidelines](./development-guidelines/README.md)
+  - [Code Maturity](./development-guidelines/code_maturity.md)
   - [High-Level Best Practices](./development-guidelines/guidelines.md)
   - [Token Integration Checklist](./development-guidelines/token_integration.md)
   - [Incident Response Recommendations](./development-guidelines/incident_response.md)

development-guidelines/README.md

@@ -1,5 +1,6 @@
 List of Best Practices for Smart Contract Development
 
+- [Code Maturity](./code_maturity.md): Criteria for developers and security engineers to use when evaluating a codebase’s maturity
 - [High-Level Best Practices](./guidelines.md): Essential high-level best practices for all smart contracts
 - [Token Integration Checklist](./token_integration.md): Important aspects to consider when interacting with various tokens
 - [Incident Response Recommendations](./incident_response.md): Guidelines on establishing an effective incident response plan