matlab-setup-worker-state

The MATLAB wrapper appears straightforward and non-malicious by itself, but it introduces meaningful risk by repeatedly dynamically loading and executing an external native library and by passing unvalidated input directly into native code. Security confidence is limited to wrapper-only visibility; the key supply-chain and runtime-integrity threats are library resolution/hijacking and any unsafe behavior in the native compute implementation.