Skip to content

chore(deps): bump com.google.crypto.tink:tink from 1.14.0 to 1.14.1 #4566

chore(deps): bump com.google.crypto.tink:tink from 1.14.0 to 1.14.1

chore(deps): bump com.google.crypto.tink:tink from 1.14.0 to 1.14.1 #4566

Triggered via pull request August 12, 2024 11:58
Status Success
Total duration 1m 3s
Artifacts

kics.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
[MEDIUM] Container Traffic Not Bound To Host Interface: samples/edc-dast/docker-compose.yaml#L30
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Healthcheck Not Set: samples/edc-dast/docker-compose.yaml#L24
Check containers periodically to see if they are running properly.
[MEDIUM] Host Namespace is Shared: samples/edc-dast/docker-compose.yaml#L24
The hosts process namespace should not be shared by containers
[MEDIUM] Memory Not Limited: samples/edc-dast/docker-compose.yaml#L24
Memory limits should be defined for each container. This prevents potential resource exhaustion by ensuring that containers consume not more than the designated amount of memory
[MEDIUM] Security Opt Not Set: samples/edc-dast/docker-compose.yaml#L24
Attribute 'security_opt' should be defined.
[LOW] Container Capabilities Unrestricted: samples/edc-dast/docker-compose.yaml#L24
Some capabilities are not needed in certain (or any) containers. Make sure that you only add capabilities that your container needs. Drop unnecessary capabilities as well.
[LOW] Cpus Not Limited: samples/edc-dast/docker-compose.yaml#L24
CPU limits should be set because if the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests