mirror of
https://github.com/thedevs-network/kutt-extension.git
synced 2026-02-03 05:43:24 +00:00
Kutt Extension has been flagged and disabled by Chrome Web Store #4
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @adan89lion on GitHub.
Description:
Kutt Extension has been automatically disabled (and locked) on my Edge browser on macOS on July 10th, 2022. Its page on Chrome Web Store has also been removed. (I've attached the screenshot of the alert on Edge browser).
Device info:
@abhijithvijayan commented on GitHub:
@poeti8 any ideas on what caused the rejection?
I will land a PR with all dependencies upgrade for the extension. Maybe that will help?
@imakiro commented on GitHub:
No update on the rejection from stores, bugfix releases ?
@hammady commented on GitHub:
How is this report related to the kutt server itself? It seems to be a different repo. We need a prompt explanation in case the kutt server has serious security issues and must be taken down.
@lukasgabriel commented on GitHub:
I also noticed this yesterday on Edge.
The extension was also removed from the Firefox Addon Store: https://addons.mozilla.org/firefox/addon/kutt/
Can anyone provide info about whether this is a false positive and the extension can safely be re-enabled, or is there actually malware present? Is there any reason to also be worried about the main repo? I've shut down my self-hosted Kutt instance, just to be safe, until there's a response from the developers.
@moquito64 commented on GitHub:
Edge, Chrome, and Firefox all seem to have flagged this as containing malware. Hope we get more information soon. I have disabled this until further notice.
@Tnology commented on GitHub:
Any update on this? I just got my selfhosted Kutt service up and running, and I'm super excited to use this (especially for custom domains like [my domain].com/apply alongside all of the other useful features).
@poeti8 commented on GitHub:
@abhijithvijayan any updates on this?
@poeti8 commented on GitHub:
@abhijithvijayan This is the email I got from Firefox:
And for Chrome:
@abhijithvijayan commented on GitHub:
will migrate to v3 soon and we can go ahead with the release which would resolve this.
I will add the missing permission to the manifest as well so that this issue is rectified.
@abhijithvijayan commented on GitHub:
this is blocked on the migration of the plugin i wrote to support webpack 5. https://github.com/abhijithvijayan/wext-manifest-webpack-plugin
Webpack has introduced major breaking changes and deprecated APIs relied on by the plugin. Once I manage to get it migrated, I will pick this issue up.
@poeti8 commented on GitHub:
You can use it if you have already installed it.
I'll check with the issue myself soon, seems like @abhijithvijayan doesn't have free time.
@poeti8 commented on GitHub:
Can't we use something else for now? Or take another approach?
@lukasgabriel commented on GitHub:
@poeti8 You can still use the plugin just fine.
@brianantonelli commented on GitHub:
No, you can't use it just fine. It's missing from the store.
@mtan93 commented on GitHub:
You can install manually by downloading the chrome.zip release, enable developer mode and drop the extracted folder into the chrome://extensions page.
@poeti8 commented on GitHub:
Kutt is now back on Chrome Web Store: https://chrome.google.com/webstore/detail/kutt/pklakpjfiegjacoppcodencchehlfnpd
Firefox review is still pending.
@poeti8 commented on GitHub:
@abhijithvijayan That's good news. I appreciate the work you have done so far, but can we completely remove the build the step? I wouldn't want it any other way. Just like the Kutt version 3, I wanted to get rid of all the build steps for the extension and use simple HTML/CSS and only htmx perhaps—without React or any other framework—to prevent similar issues from happening in future.
@poeti8 commented on GitHub:
For FireFox? I submitted many times but each time they respond with something weird that I don't know how to fix. I should try again soon.
@abhijithvijayan commented on GitHub:
I am re-writing the underlying repo https://github.com/abhijithvijayan/web-extension-starter to work with v3 manifest extensions. Will migrate this repo to use the new build setup and get a version built. Once that is done, this extension can be published to stores once again. Sorry that it took me some time to get back to working on the project(i had gotten a fulltime job which didn't let me do anything really for couple of years, which is not the case anymore).
Progress branch: https://github.com/abhijithvijayan/web-extension-starter/tree/vite-rewrite
Updates posted on thread: https://github.com/abhijithvijayan/web-extension-starter/issues/66
cc: @poeti8
@Lancaban commented on GitHub:
Any updates on this yet?
@abhijithvijayan commented on GitHub:
This was not exactly an issue with the libraries, it was because of chrome deprecating Manifest v2 way faster than other browsers leading to partial support. Now major browsers have manifest v3 support, so I have made every change to support this in https://github.com/thedevs-network/kutt-extension/pull/138.