GitProxy Plugin: Detect the usage of Non-Standard Cryptography Implementation

[ChaitanyaD48]

Issue :
Currently, GitProxy lacks specific checks to detect the use of non-standard or potentially insecure cryptography practices within codebases. It is concerning when code containing these practices is pushed to repositories, potentially leading to serious compliance and security issues. Developing a mechanism to automatically identify such instances would greatly enhance the security measures in place during the code review process.

Solution :
I would like to develop a new plugin for GitProxy that analyzes code for the usage of non-standard cryptography or encryption techniques. This plugin would scan the git diff input and provide informational or advisory outputs regarding any detected instances of insecure cryptographic practices, thus ensuring developers are aware of potential vulnerabilities before their code is pushed to the repository.

Alternatives :
Currently, developers can manually review their cryptographic implementations or rely on external static analysis tools. However, these methods are often time-consuming and may not seamlessly integrate with the existing GitProxy workflow. I believe that incorporating this plugin into GitProxy would provide a more efficient and automated solution, streamlining the security scanning process without requiring additional manual steps.

This feature would significantly enhance the security using GitProxy by proactively identifying risky Non-Standard Cryptographic Implementations.