Skip to content

CI: Add workflow to create svg puml #244

CI: Add workflow to create svg puml

CI: Add workflow to create svg puml #244

Triggered via pull request October 30, 2023 10:10
Status Success
Total duration 1m 23s
Artifacts

kics.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
[MEDIUM] Container Running With Low UID: charts/puris/charts/backend/templates/deployment.yaml#L1
Check if containers are running with low UID, which might cause conflicts with the host's user table.
[MEDIUM] Container Running With Low UID: charts/puris/charts/frontend/templates/deployment.yaml#L1
Check if containers are running with low UID, which might cause conflicts with the host's user table.
[MEDIUM] Container Traffic Not Bound To Host Interface: backend/docker-compose.yaml#L26
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: frontend/docker-compose.yaml#L26
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Healthcheck Not Set: frontend/docker-compose.yaml#L23
Check containers periodically to see if they are running properly.
[MEDIUM] Healthcheck Not Set: backend/docker-compose.yaml#L23
Check containers periodically to see if they are running properly.
[MEDIUM] Host Namespace is Shared: frontend/docker-compose.yaml#L23
The hosts process namespace should not be shared by containers
[MEDIUM] Host Namespace is Shared: backend/docker-compose.yaml#L23
The hosts process namespace should not be shared by containers
[MEDIUM] Memory Not Limited: backend/docker-compose.yaml#L23
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] Memory Not Limited: frontend/docker-compose.yaml#L23
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