Mikael Brevik

Interesting. There's either an issue with access, or something else going on here. Are you trying to run the terminal-notifier in the vendor-folder so you know it's the same one?...

Hm. What seems to remain then is either the way it is spawned (through `execFile`) or access level. Could try setting the `uid` or `gid` options to execFile for instance.

Would be great to know if this is a problem with the actual execution, or something else we're missing. For instance, if one takes a working command and copies it...

I think this should be reported as false positive. As far as I've seen, there is no malicious code (https://www.paralint.com/projects/notifu/code.html#getthesource)

Investigating. New version stems from https://github.com/mikaelbr/node-notifier/commit/ee9c2750ae414056ce57dc6b95e4ebc6beb2a160 via https://github.com/ixe013/notifu

Maybe @ixe013 has some insight?

I reverted the commit, deprecated 5.2.0 and published a patch with the old version. Just to be on the safe side. Sorry for the inconvenience.

Brilliant. Thanks for the followup. I'll look into reupdating this

There is no automatic closing of the sub process when the mother process quits. In most cases I don't think this is a problem, when terminal-notifier works properly – but...

Sounds like it is related to #218