Making container vulnerability management more approachable.

DIP was created to make investigating and addressing known operating-system vulnerabilities in container images more approachable, particularly for users who would rather work through a graphical interface than construct and run the equivalent command-line workflows manually.

From a single interface, DIP uses Trivy to scan a selected container image and present the identified vulnerabilities in a form that is easier to inspect and understand. Results are separated into vulnerabilities for which a known fix is available and those for which no fix is currently available.

Where fixes are available, DIP then uses Copa to build a separate patched image, which can be tested before the user decides whether to deploy it.

The user remains in control.

The original container image is preserved throughout the process. When vulnerabilities with known fixes are patched, DIP creates a separate image so that it can be tested before the user decides whether to deploy it.

DIP does not automatically deploy patched images, modify Docker Compose or YAML configuration, or make changes to existing stacks. Deployment remains a deliberate user action using the tools and configuration already used to manage the container.

DIP provides no mechanism for deleting container images, including either the original image or patched images it creates. Its role ends with inspection and the creation of a patched image; testing, deployment and removal remain deliberate user decisions.