Abstract: Disclosed in some examples are methods, systems, devices, and machine-readable mediums for a dependency tracking service which automatically identifies and tracks information about dependencies of a software component and provides one or more visualizations displaying that information. The system may identify the dependencies through automated metadata analysis of the software component, behavior analysis of the software component, or source code analysis of the software component. The system may track status of the software component by reference to one or more code management systems, vulnerability reporting systems, or the like.

Abstract: Disclosed in some examples are methods, systems, devices, and machine-readable mediums for managing the testing of software component dependencies. In some examples, the system may track versions of dependencies; provide an interface to create a customized testing environment—e.g., such as by allowing a user to select whether to include a particular dependency and what version of that dependency to include; select test scripts; select test environments; and automate tests of the selected versions. The system may log test results that can be used for proof of regulatory compliance. In some examples, the system may automate the testing of new dependency versions. For example, a new version of a dependency may automatically be tested by the system using one or more test scripts. The results may then be presented to one or more users.