We are reaching out regarding the review status of the Uniqkey browser extension. We have noticed that our recent submissions have not progressed through the review process for an extended period, and we are beginning to receive inquiries from our customers as a result.
Could you kindly provide us with a status update, or let us know if there is anything we can do on our end to help expedite the process?
Hi! I’ve seen similar “stuck in review” situations — sometimes the review queue can take a few days or more depending on workload and manual checks.
It might just need a little more time, but if it’s been a while with no change, you could politely follow up with the review team or check for any missing info on your submission. Hope you get an update soon!
Thank you for your wonderful answer Adam, I really appreciate it!
@Uniqkey I am really sorry about this! Unfortunately, we are experiencing a huge influx of add-on submissions daily, which has resulted in a long review queue. I will let the review team know, and hopefully you will have news soon!
I submitted a version on March 1st that was awaiting review until I submitted a new version on March 22nd, and now 20 days later or so that version is still awaiting review. Is this the expected timeline - at least three weeks to have something reviewed? I was looking for a support email and came across this forum and it seems like a pretty frequent query, but just wondering if you can help me get an idea on time required from release to get review.
I believe that if you need to package or minify the add-on, the source code is required, which can extend the review period. I recently submitted a new add-on as well, but this one has to be minified to keep it compact. I expect the review process may take around one to two months.
For context: we’ve been in the review queue since March 23, 2026 with no reviewer response. The submission includes the full source package and detailed reviewer notes, and all issues raised in the previous review cycle have already been addressed. At this point we’re just waiting on someone to pick it up.
Cool, thanks for the info, it is a source code required situation and we try to provide detailed notes. I guess based on @Uniqkey comment this is 1-2 months for every update going forward also?
I can’t speak in an official capacity, but from reading through some of the community posts, non-source-code add-ons can take anywhere from 3 to 14 days, usually closer to 3. Manually reviewed source code submissions will likely take twice as long due to the nature of their packaging and auditing.
You should also keep in mind that this is Mozilla — not a massive conglomerate with infinite funding like Google, Apple, or Microsoft — but still very much one of the best organizations the web has to offer when it comes to user empowerment.
At least two of the consistent team members have recently mentioned delays due to the size of the current queue, so if anything, I’d hold off at least 20 full business days before sending a check-in or status email to the add-ons mailbox.
They do have one, and you’ll likely get a faster response there as well.
I can confirm that we currently have the longest queue that we have had in the last six months. The size of the new add-ons in the review queue has been increasing rapidly.
And that’s due to a lot of different factors, but the ones that are affecting us the most are the following:
It’s easier than ever for someone to write a new add-on and publish it.
It’s easier than ever for people to build bots and fake users.
As a result, malicious attacks have become more common than ever, with a recent example publicized last week.
Our top priority is the safety of our users and developers; that’s why we are continuously working to address the issues that have arisen recently while protecting them/you. Our manual review times currently vary from a few days to a few weeks, but it is worth mentioning that only a percentage of the daily submitted add-ons are added to the manual review queue. And that’s because the majority of the versions submitted to addons.mozilla.org, are fully compliant with our policies.
I am not saying that the add-ons going to the manual review queue are not compliant, but sometimes it’s difficult for our automated tools to validate that our policies are fully met; that’s why they are sent to manual human review. Also, it is worth noting that manual review times depend on the nature of the add-on, its implementation, and the instructions provided to our reviewers for building it. We have had many cases in the past where reviewers took way more time to build the add-on than to review its code and logic. Lastly, when the code is obscured, it’s always more difficult for our reviewers to read, understand, and review it quickly.
That said, we all appreciate the patience you have been showing as we work to improve our processes, identify and restrict malicious users and add-ons, and ensure the quality and safety of the ecosystem. I am confident that we will soon stabilize the situation and drastically reduce waiting times, allowing you to ship changes faster.
My extension orange-juice-hn has stopped receiving reviews. It is fully compliant with zero errors or warnings and a good history. Last success was April 23rd. Just hoping the queue eases up a bit and gets to me. Thanks!
We are doing our best to navigate this new situation, and we have made significant progress over the past few weeks. However, we can’t scale as quickly as thousands of users submitting enormously large add-ons.
I appreciate your patience, and I am really sorry for the delays. I really wish things were different. And trust me, we are doing our best to tackle the situation as quickly as possible, always keeping the safety of our users and developers in mind.
Thanks for the answer @mozchris. The solution seems simple though. Sort the queue based on age of project, errors, users, etc., then process it. The AI spam submissions will quickly go to the bottom.
There should also be a preference for projects like mine that reach out to you here that are obviously in need of some help.
Over a month to get a new version out is kind of crazy and is going to end up destroying your extension community. Why would I care about Mozilla if I can’t even get a new version out? I’ll just focus on Chrome instead.
If we were to expedite reviews for people who are reaching out, we would have to incentivize people to contact us, which would mean a lot of additional work on our side to see the message, address it, and respond.
I could play devil’s advocate and argue for sorting the queue by the number of users or active developers rather than by project age. Why give special treatment to someone who published an add-on 10 years ago but hasn’t pushed an update since, and not to the developer who pushes updates every month?
I am not saying we are doing this; I am just saying it’s a bit trickier than you and I would like it to be. And especially because AI is currently used by literally everyone, not just spammers.
On why you should care about Mozilla: because we are working on building an open web for everyone. We take the security of our users and developers really seriously, and we don’t require you to have a credit card and pay $5 to publish your Add-on. For some people, $5 might be a cup of coffee, but for most people around the world, $5 is a meal.
And trust me, everyone, that I know at Mozilla cares about details like these. We care about our people, our users, and you, the developers. We don’t have a help center like Chrome’s to read an article to get an answer. We have a lively Discourse where people can interact, connect, and get support. Because we care! And we will figure this out. We will decrease the manual review times. I just want to ask you for a little bit of patience. We will get there, I promise!
I get that things are complex, but look at my history. Does this entitle me to over a month delay? How about thinking about how this impacts my own ever shrinking set of users? They try it, find a bug and then uninstall because of something that was fixed over a month ago.
The $5 was actually refunded to me without me even asking. Maybe Mozilla should actually put up a bit of a barrier like that because what you’re doing now, isn’t working. I also seriously doubt that someone who can’t afford $5 is busy building quality extensions. I’ve got nearly 1000 unit tests in my open source repo. There are an infinite number of things you can sort the queue on and speed this process up for the ones who are taking this seriously and not just submitting slop.
Hey, mozilla admins
joining the thread of “stucks”. We actually have several add-ons that are published as unlisted and listed. And only one gets stuck in reviews (probably to its history) can this be changed? I mean like, flags that mark it for manual review, aren’t set for all our add-ons, but the specific one that actually cases client disturbance.
Pls help
I’ve seen similar “stuck in review” situations — sometimes the review queue can take a few days or more depending on workload and manual checks.
