[BE][FE][SECURITY] Kics #985
Annotations
10 warnings
|
KICS scan:
tx-backend/openapi/traceability-foss-backend.json#L13
Global server object URL should use 'https' protocol instead of 'http'
|
|
KICS scan:
tx-backend/openapi/traceability-foss-backend.json#L1393
The Media Type Object should have the attribute 'schema' defined
|
|
KICS scan:
tx-backend/openapi/traceability-foss-backend.json#L451
The Media Type Object should have the attribute 'schema' defined
|
|
KICS scan:
tx-backend/openapi/traceability-foss-backend.json#L1509
The Media Type Object should have the attribute 'schema' defined
|
|
KICS scan:
tx-backend/openapi/traceability-foss-backend.json#L3905
500, 429 and 400 responses should be defined for all operations, except head operation. 415 response should be defined for the post, put, and patch operations. 404 response should be defined for the get, put, head, delete operations. 200 response should be defined for options operation. 401 and 403 response should be defined for all operations when the security field is defined.
|
|
KICS scan:
tx-backend/openapi/traceability-foss-backend.json#L3905
500, 429 and 400 responses should be defined for all operations, except head operation. 415 response should be defined for the post, put, and patch operations. 404 response should be defined for the get, put, head, delete operations. 200 response should be defined for options operation. 401 and 403 response should be defined for all operations when the security field is defined.
|
|
KICS scan:
tx-backend/openapi/traceability-foss-backend.json#L3905
500, 429 and 400 responses should be defined for all operations, except head operation. 415 response should be defined for the post, put, and patch operations. 404 response should be defined for the get, put, head, delete operations. 200 response should be defined for options operation. 401 and 403 response should be defined for all operations when the security field is defined.
|
|
KICS scan:
tx-backend/openapi/traceability-foss-backend.json#L3905
500, 429 and 400 responses should be defined for all operations, except head operation. 415 response should be defined for the post, put, and patch operations. 404 response should be defined for the get, put, head, delete operations. 200 response should be defined for options operation. 401 and 403 response should be defined for all operations when the security field is defined.
|
|
KICS scan:
tx-backend/openapi/traceability-foss-backend.json#L3905
500, 429 and 400 responses should be defined for all operations, except head operation. 415 response should be defined for the post, put, and patch operations. 404 response should be defined for the get, put, head, delete operations. 200 response should be defined for options operation. 401 and 403 response should be defined for all operations when the security field is defined.
|
|
KICS scan:
tx-backend/openapi/traceability-foss-backend.json#L3905
500, 429 and 400 responses should be defined for all operations, except head operation. 415 response should be defined for the post, put, and patch operations. 404 response should be defined for the get, put, head, delete operations. 200 response should be defined for options operation. 401 and 403 response should be defined for all operations when the security field is defined.
|
The logs for this run have expired and are no longer available.
Loading