Monitoring a software development pipeline

1 . A method of monitoring a software development pipeline, the method comprising:

retrieving information describing actions performed by one or more components during execution of the software application in a software development pipeline;

identifying an anomaly associated with the software application based on the information;

displaying one or more dependencies associated with the software application in a plurality of polygraphs as icons in a user interface, including:

displaying a first polygraph reflects a first relationship between the one or more components during a first instance in time; and

displaying a second polygraph reflects a second relationship between the one or more components during a second instance in time, wherein the first relationship is different than the second relationship; and

displaying an alert icon within a polygraph to identify the anomaly within the one or more dependencies.

2 . The method of claim 1 wherein identifying the anomaly associated with the software application further comprises:

identifying the one or more dependencies for the software application; and

identifying, as the anomaly associated with the software application, an anomaly associated with the one or more dependencies.

3 . The method of claim 2 wherein the anomaly associated with the one or more dependencies comprises a vulnerability in the one or more dependencies.

4 . The method of claim 2 wherein the one or more dependencies for the software application comprise one or more build-time dependencies.

5 . The method of claim 1 further comprising blocking deployment of the software application.

6 . The method of claim 1 further comprising rolling back a deployment of the software application.

7 . The method of claim 1 wherein identifying the anomaly associated with the software application further comprises:

correlating another anomaly associated with an execution of the software application with one or more actions in the software development pipeline; and

identifying, as the anomaly associated with the software application, the one or more actions.

8 . The method of claim 1 wherein the information comprises an action performed by each of the one or more components.

9 . The method of claim 1 wherein a first icon comprises an application and a second icon comprises a service.

10 . The method of claim 1 wherein a first icon comprises a source code file and a second icon comprises a code branch.

11 . A system comprising one or more processors to execute one or more instructions, which cause the processor to monitor a software development pipeline, comprising:

retrieving information describing actions performed by one or more components during execution of the software application in the software development pipeline;

identifying an anomaly associated with the software application based on the information;

displaying one or more dependencies associated with the software application in a plurality of polygraphs as icons in a user interface, including:

displaying a first polygraph reflects a first relationship between the one or more components during a first instance in time; and

displaying a second polygraph reflects a second relationship between the one or more components during a second instance in time, wherein the first relationship is different than the second relationship; and

displaying an alert icon within a polygraph to identify the anomaly within the one or more dependencies.

12 . The system of claim 11 wherein identifying the anomaly associated with the software application further comprises:

identifying the one or more dependencies for the software application; and

identifying, as the anomaly associated with the software application, an anomaly associated with the one or more dependencies.

13 . The system of claim 12 wherein the anomaly associated with the one or more dependencies comprises a vulnerability in the one or more dependencies.

14 . The system of claim 12 wherein the one or more dependencies for the software application comprise one or more build-time dependencies.

15 . The system of claim 11 wherein the one or more processors to execute one or more instructions, which further cause the processors to block deployment of the software application.

16 . The system of claim 11 wherein the one or more processors to execute one or more instructions, which further cause the processor to roll back a deployment of the software application.

17 . The system of claim 11 wherein identifying the anomaly associated with the software application further comprises:

correlating another anomaly associated with an execution of the software application with one or more actions in the software development pipeline; and

identifying, as the anomaly associated with the software application, the one or more actions.

18 . The system of claim 11 wherein a first icon comprises an application and a second icon comprises a service.

19 . The system of claim 11 wherein a first icon comprises a source code file and a second icon comprises a code branch.

20 . A non-transitory machine-readable medium having instructions, which when executed by one or more processors, cause the one or more processors to:

retrieve information describing actions performed by one or more components during execution of a software application in a software development pipeline;

identify an anomaly associated with the software application based on the information;

display one or more dependencies associated with the software application in a plurality of polygraphs as icons in a user interface, including:

displaying a first polygraph reflects a first relationship between the one or more components during a first instance in time; and

displaying a second polygraph reflects a second relationship between the one or more components during a second instance in time, wherein the first relationship is different than the second relationship; and

display an alert icon within a polygraph to identify the anomaly within the one or more dependencies.