Skip to content
Semgrep SAST Scan

Add workflow_call support in unittests workflow #20

Sign in to view logs

Add workflow_call support in unittests workflow

Add workflow_call support in unittests workflow #20

Triggered via pull request May 8, 2025 10:01
@JSabadinJSabadin
synchronize #149
feat/add-workflow_call-to-unittests
Status Success
Total duration 35s
Artifacts –

semgrep.yaml

on: pull_request
semgrep/ci
25s
semgrep/ci
Fit to window
Zoom out
Zoom in

Annotations

6 errors
Semgrep Issue: tools/yolo/yolov5_exporter.py#L30
Functions reliant on pickle can result in arbitrary code execution. Consider loading from `state_dict`, using fickling, or switching to a safer serialization method like ONNX
Semgrep Issue: tools/yolo/yolov6_exporter.py#L29
Functions reliant on pickle can result in arbitrary code execution. Consider loading from `state_dict`, using fickling, or switching to a safer serialization method like ONNX
Semgrep Issue: tools/yolov6r1/yolov6_r1_exporter.py#L28
Functions reliant on pickle can result in arbitrary code execution. Consider loading from `state_dict`, using fickling, or switching to a safer serialization method like ONNX
Semgrep Issue: tools/yolov6r3/gold_yolo_exporter.py#L33
Functions reliant on pickle can result in arbitrary code execution. Consider loading from `state_dict`, using fickling, or switching to a safer serialization method like ONNX
Semgrep Issue: tools/yolov6r3/yolov6_r3_exporter.py#L40
Functions reliant on pickle can result in arbitrary code execution. Consider loading from `state_dict`, using fickling, or switching to a safer serialization method like ONNX
Semgrep Issue: tools/yolov7/yolov7_exporter.py#L29
Functions reliant on pickle can result in arbitrary code execution. Consider loading from `state_dict`, using fickling, or switching to a safer serialization method like ONNX