Skip to content

Feat: Add API Key security #310

Feat: Add API Key security

Feat: Add API Key security #310

Triggered via pull request November 20, 2023 17:46
Status Success
Total duration 1m 8s
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: frontend/docker-compose.yaml#L26
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: local/daps/docker-compose.yaml#L26
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: local/docker-compose.yaml#L179
Incoming container traffic should be bound to a specific host interface
[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: local/docker-compose.yaml#L26
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: local/docker-compose.yaml#L244
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: local/docker-compose.yaml#L46
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: local/docker-compose.yaml#L46
Incoming container traffic should be bound to a specific host interface