Hi @jimlongo & @ottomek,
Dylan here from the development team, one of the lead developers on the project.
Thank you for getting in touch, and reporting the issue to us. I was made aware of this earlier today and have audited the core code base.
I am happy to report that this issue does not affect our plugin as we do not include the compromised library. More specifically, we do not use the polyfill library or any cloud based polyfill alternatives that are known to be compromised.
You can confidently continue to use our plugin without any additional action, however, we will continue to monitor the situation and react to any changes in the list of exposed assets, although we do not expect any issues based on the current information available.
If you do have any further concerns, please send these over to me and I’d gladly take a closer look.
