Skip to content

feature: #837 use digitalTwinType for shell lookup, #603 upgrade aspect models #1259

feature: #837 use digitalTwinType for shell lookup, #603 upgrade aspect models

feature: #837 use digitalTwinType for shell lookup, #603 upgrade aspect models #1259

Triggered via pull request May 2, 2024 10:46
Status Success
Total duration 53s
Artifacts

kics.yml

on: pull_request
Analyze frontend
39s
Analyze frontend
Analyze backend
42s
Analyze backend
Fit to window
Zoom out
Zoom in

Annotations

15 warnings
[MEDIUM] Container Capabilities Unrestricted: frontend/cypress/docker-compose.yml#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.
[MEDIUM] Container Capabilities Unrestricted: frontend/docker-compose.yml#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.
[MEDIUM] Healthcheck Not Set: frontend/cypress/docker-compose.yml#L24
Check containers periodically to see if they are running properly.
[MEDIUM] Host Namespace is Shared: frontend/docker-compose.yml#L45
The hosts process namespace should not be shared by containers
[MEDIUM] Shared Host Network Namespace: frontend/cypress/docker-compose.yml#L35
Container should not share the host network namespace
[MEDIUM] Global Server Object Uses HTTP: tx-backend/openapi/traceability-foss-backend.json#L1
Global server object URL should use 'https' protocol instead of 'http'
[MEDIUM] Media Type Object Without Schema: tx-backend/openapi/traceability-foss-backend.json#L1
The Media Type Object should have the attribute 'schema' defined
[MEDIUM] Media Type Object Without Schema: tx-backend/openapi/traceability-foss-backend.json#L1
The Media Type Object should have the attribute 'schema' defined
[INFO] Invalid Media Type Value (v3): tx-backend/openapi/traceability-foss-backend.json#L1
The Media Type value should match the following format: <type>/<subtype>[+suffix][;parameters]
[INFO] Invalid Media Type Value (v3): tx-backend/openapi/traceability-foss-backend.json#L1
The Media Type value should match the following format: <type>/<subtype>[+suffix][;parameters]
[INFO] Invalid Media Type Value (v3): tx-backend/openapi/traceability-foss-backend.json#L1
The Media Type value should match the following format: <type>/<subtype>[+suffix][;parameters]
[INFO] Invalid Media Type Value (v3): tx-backend/openapi/traceability-foss-backend.json#L1
The Media Type value should match the following format: <type>/<subtype>[+suffix][;parameters]
[INFO] Invalid Media Type Value (v3): tx-backend/openapi/traceability-foss-backend.json#L1
The Media Type value should match the following format: <type>/<subtype>[+suffix][;parameters]
[INFO] Operation Without Successful HTTP Status Code (v3): tx-backend/openapi/traceability-foss-backend.json#L1
Operation Object should have at least one successful HTTP status code defined
[INFO] Operation Without Successful HTTP Status Code (v3): tx-backend/openapi/traceability-foss-backend.json#L1
Operation Object should have at least one successful HTTP status code defined