RE: Avast Alert--- ALL CLEAR ;)

[jbarkls]

ran file through seven detectors, all reported the same alert at the same checkpoint in the file...
Did OPSWAT deep dive and found what I'll paste below... It seems 'NSIS_Error' is related to an addressing error in a file call path (SSDEEP)? that throws a 404..
HTML document showed a soft 404 page at URL: http://nsis.sf.net/NSIS_Error

Final Analysis:
Deep dive is clean, there are 'cautions' due to what clearly are necessary under-the-hood reg, api, sys-info calls.

Have sent to Avast to evaluate and clear as false-positive on their end..

JB

[PurpleDoubleD]

hey @jbarkls, real talk — thanks for the deep dive. seven scanners + an OPSWAT analysis + a false-positive report over to avast is more due diligence than i would've done myself. this is exactly what the project needs.

on the cause: the NSIS_Error addressing-call trigger is a known avast heuristic pattern that false-positives on a lot of NSIS installers. the exe we ship gets signed with our tauri updater key (see releases), but the main setup installer is still unsigned — proper code-signing cert is pending. EV cert is on the list once the project justifies it.

if anyone else sees a virustotal flag, the avast deep-scan path is reliably clean — like you proved.

thanks again, stay on the radar.