On 04 Apr 2024, at 09:15, giova...@paclan.it wrote: > We might have a similar issue in SpamAssassin, we have code to detect > anomalies in .xls and .xlsx files > but we do not have any way to create those files (that might contain macros) > in the build process.
In this case testing should be moved out into a separate project, unrelated to the artefact being built. The blunt "no weird binaries in our releases" (because the weird binaries are kept outside the releases) is very simple to audit. Regards, Graham --
