How to pass extension moderation in AMO?

Question

JavaScript

Good afternoon,

I've been developing a small extension for VK since 2016. It all started as a small design improvement, but then it grew into something more.

The extension was added to the Firefox store in October 2019 - before that there was no version for this browser, hands did not reach.

Accordingly, most likely there were no reports for the extension during this time, because in fact there is nothing for it, everything is implemented there only what is stated in the description, nothing harmful is done, data about users is not collected.

But a month ago, someone at the top decided to schedule a manual check. By a strange coincidence, this happened after my other extension was returned to the store, which also "walked on the edge" due to the use of eval and was blocked for a year (this is not something malicious, but a tool for testing third-party sites inside the sandbox , if you are interested, you can search in the stores by the name "Lightning").

So, according to the results of the check, the extension for VK, which is completely harmless in terms of permissions in the manifest and code, was frozen under the pretext that the famous decryption code is used therelinks to audio files - and motivating not by the fact that the DMCA is violated, but by the fact that the code is allegedly minified. It’s hard to argue with the latter, but firstly, the code is in a bunch of public sources and everyone in the web community knows what it does, and secondly, it is quite transparent in the sense that it does not manipulate cookies, the network, or window objects /document does not use eval. And thirdly, almost any code that implements even the simplest cryptography will look very similar.

All of this makes me feel like I'm just being trolled. The correspondence dragged on for more than a month, I tried to make several versions of this piece of code with improved variable names and more simplified syntax, removing the obvious consequences of the minifier, but this was ignored and I received a block.

Actually, what can be done? Has anyone experienced this?

So far, everything is fine in the Chrome Store, but Firefox support is important to me, and I don’t want to completely remove the track download function.