Abstract: Mechanisms for determining security compliance of continuous build software are provided. In some embodiments, the mechanisms comprise: receiving a trigger at a hardware processor from a continuous build tool indicating that code has been created or updated; receiving a code template corresponding to the code at the hardware processor; checking the code template against a plurality of policies to determine if there is a security violation; and indicating that the code template has passed a compliance check prior to a code stack for the template being built by the continuous build tool.