Abstract: A system and method enhancing source code management with existing virus detection methods in a library management system to detect potentially malicious code. Malicious code that is introduced into a software product may be detected before the code is able to damage stored data and other software by preventing a product build with the malicious code. Source code received at a code management library system from a set of software developers in a collaborative development environment is moved into a staging area. A determination is made in the staging area as to whether malicious code exists in the source code. If malicious code exists, the library management system does not forward the source code to the software product build and notifies a system administrator of the presence of the malicious code.

Abstract: A repair mechanism within a code management library system for repairing build code that is infected with malicious code. When a virus pattern is detected in a component of a source code, other components in the source code containing dependencies upon the first component are identified. This identification may be based on rules defined from relationships between the infected component and the other components in the source code. The component and the other components that are identified as having dependencies upon the infected component are retracted from the software product build. The infected component and the other identified components are then replaced with a previous archive of the code build. The software product build of the source code may then be performed.