We successfully contacted the author. He is currently working on patching the issue in the next version.