While there is still the chance that it will go through, it is more likely that it too will be rejected by Google and that this could effectively end uBlock Origin for Google Chrome. The main issue with the rejection is that the next stable version of the extension will be more or less identical to the rejected developer version.

The developer version of the extension is used by fewer users than the stable version which means that the rejection does not affect the bulk of users of the extension yet. No point speculating one way or another, my experience with the CWS in the past is that we will never know why it was labelled 'REJECTED', they never disclose the exact 'why'. Hill, a long-time developer, had no illusions that Google would provide actionable information about the rejection. The email provides no information on the actual violation other than that, a practice that Google has been criticized for in the past. In an email to the developer, Google stated that the extension violated one of the Chrome Store's policies that prohibits the bundling of unrelated functionality in extensions. Developers upload new extension versions to the Chrome Web Store to replace existing versions Google runs automated scans of these tools and may also look at the uploaded extensions manually before allowing or rejecting them. Raymond Hill (gorhill), the developer of uBlock Origin revealed recently that Google rejected a new developer version of the extension. Update: uBlock Origin Dev is now available again on the Chrome Web Store. Google changed some parameters after it faced heavy user and developer criticism but did not revert the course completely. The new manifest file for Chrome extensions could end extensions like uBlock Origin for the web browser.

Ublock origin edge chromium