Thanks for the response Patrick, the broader use case is essentially:
Automatically run a security assessment on code as the code is (attempted-ly) being "checked-in" to a repository and if vulnerabilities are found do not allow the "check-in", rather report the vulnerabilities in some way/shape/form. The reporting would preferably be documented for historic reference. Thus the use of DevInspect will be enforced prior to code entering the repository.