Version 2.0 View in Chrome Web Store
The extension has a moderate user base of 40,000 users and a decent rating of 3.9/5, suggesting some level of community acceptance. The purpose of detecting WordPress themes and plugins is legitimate and useful for web developers and security professionals. However, the relatively low number of reviews (55) compared to the user count raises questions about user engagement.
The extension's broad content script injection capability across all URLs is concerning given its specific WordPress-focused purpose. While tabs permission is necessary for the extension's functionality, the combination with universal content script access creates significant privacy and security risks. The extension could potentially access sensitive information on any website, not just WordPress sites. The lack of host permission restrictions means there are no technical safeguards limiting which sites the extension can interact with.
Consider running this extension in a separate Chrome profile dedicated to web development work to isolate potential risks from your main browsing activities. Only enable the extension when actively analyzing WordPress sites, and disable it during regular browsing. Monitor the extension's behavior and be cautious about using it on sites containing sensitive information. Given the legitimate use case, the risks may be acceptable for web professionals who need this functionality, but casual users should consider whether the benefits outweigh the security implications.
| https://developer.chrome.com/extensions/tabs#type-Tab | https://scanwp.net/extension/?url= | |
| https://clients2.google.com/service/update2/crx | 
{ "name": "Scan WP - WordPress Theme and Plugin Detector", "action": { "default_icon": "icon.png", "default_popup": "Popup.html" }, "version": "2.0", "update_url": "https://clients2.google.com/service/update2/crx", "permissions": [ "tabs" ], "content_scripts": [ { "js": [ "jquery.min.js" ], "run_at": "document_end", "matches": [ "<all_urls>" ] } ], "manifest_version": 3, "content_security_policy": { "extension_pages": "script-src 'self'; object-src 'self'" } }