Dependency-track Helm Chart

Dependency-track
Analyzed version: 1.3.5

By davidkarlsen

Dependency-Track is an intelligent Software Supply Chain Component Analysis platform that allows organizations to identify and reduce risk from the use of third-party and open source components. Dependency-Track takes a unique and highly beneficial approach by leveraging the capabilities of Software Bill-of-Materials (SBOM). This approach provides capabilities that traditional Software Composition Analysis (SCA) solutions cannot achieve.

Prometheus, a CNCF project, is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true.

This chart bootstraps a Prometheus deployment on a Kubernetes cluster using the Helm package manager.

Latest version: 15.5.3
View GitHub

How to Install the Dependency-track Helm Chart

Add Chart Repository to Helm

helm repo add evryfs-oss https://evryfs.github.io/helm-charts/

Install Chart

helm install my-dependency-track evryfs-oss/dependency-track --version 1.3.5

Does the Dependency-track chart contain security gaps?

The chart meets the best practices recommended by the industry.

The chart contains 4 misconfigurations.

The chart meets the best practices recommended by the industry. Find the full list of best practices here.

❌ Prevent workload from using the default namespace

1 occurrences:

  • metadata.name: release-name-postgresql (kind: StatefulSet)

💡 Incorrect value for key `namespace` - use an explicit namespace instead of the default one (`default`)

Learn how to fix the issue here

❌ Prevent container security vulnerability (CVE-2021-25741)

2 occurrences:

  • metadata.name: release-name-postgresql (kind: StatefulSet)

💡 Forbidden property object `subPath` - malicious users can gain access to files & directories outside of the volume

Learn how to fix the issue here

❌ Ensure each container has a configured memory limit

1 occurrences:

  • metadata.name: release-name-postgresql (kind: StatefulSet)

💡 Missing property object `limits.memory` - value should be within the accepted boundaries recommended by the organization

Learn how to fix the issue here

❌ Ensure each container has a configured CPU limit

1 occurrences:

  • metadata.name: release-name-postgresql (kind: StatefulSet)

💡 Missing property object `limits.cpu` - value should be within the accepted boundaries recommended by the organization

Learn how to fix the issue here

This is some text inside of a div block.
This is some text inside of a div block.

Reveal misconfigurations within minutes

3 Quick Steps to Get Started