Why tflite files are marked suspecious
This model has 4 files scanned as suspicious.
Hide files
yolo26n-seg-int8-smart.imx95.tflite
yolo26n-seg-int8.imx95.tflite
yolo26s-seg-int8-smart.imx95.tflite
yolo26s-seg-int8.imx95.tflite
Could you share details such as the scanners logs? I see nothing myself though the fact these are all imx95.tflite makes me suspect the scanner is getting tripped up by the custom Neutron ops?
Sorry, I see what you're referring to now. It looks like the tool is complaining about exactly that, the custom Neutron ops. We will look into getting that cleared but if you're concerned about the warning you can re-convert the base .tflite models to .imx95.tflite using the eIQ Neutron SDK. The .imx95.tflite models we publish convert the quantized .tflite into the .imx95.tflite with this Neutron custom operator embedded in them, this is what the NPU itself loads.