Heavily used extension keeps being rejected

[Asaf Shochet]

Hi,

We have a Chrome Extension that has been live and widely used by our customers for over six years.
A few weeks ago, we updated it, but it was rejected by the Chrome Web Store due to a violation of MV3 rules (remote code execution by a third-party library), even though this code was not new.

We fixed the issue by removing the library, yet we continue to be rejected.
I would greatly appreciate your help—if there’s someone we could speak with directly, that would be amazing.

Here is the extension ID: bomniclnnhnbdamcinadifdhkagmjkfd

Additionally, I have a few questions that aren't entirely clear to me. If you could share insights based on your experience, it would be very helpful:

1. The 30-day countdown before removal from the store—does it start from the first rejection, or is it reset each time we submit an update?
2. Why is code being rejected for containing a link inside a comment? In our case, the comment included a link, but it was not used in any way.
3. It has been five days since we submitted our update, and we still haven’t received a response (approval or rejection). This delay is frustrating.
4. Is there a sandbox, a testing environment or a utility where we can check compliance before publishing?

Thank you very much,
Asaf