Media
4 items
Description
Scan your Chrome extension .zip or .crx for Web Store rejection risks before you submit. 100% local, your code never uploads. CWS Submission Copilot scans your Chrome extension before you submit it, so a rejection does not cost you a week. Drop in your .zip or .crx and get an instant, plain-English readiness report: every likely Chrome Web Store rejection reason, the exact file it lives in, and how to fix it. The scan runs 100% in your browser. Your code never uploads anywhere. 🚀 🚀 WHY THIS CHROME EXTENSION CHECKER IS DIFFERENT Google's reviewers read your code, then send a vague rejection email that rarely tells you which line failed. CWS Submission Copilot tells you. It unzips your package locally and checks it against the real Chrome Web Store policies, naming the internal policy code for each issue (Blue Argon, Purple Potassium, Yellow Argon, Red Nickel and more) so you know exactly what a reviewer will flag. No upload, no account, no waiting. ⚡ EVERYTHING IN THE FREE PLAN ✓ Scan any Chrome extension .zip or .crx and get a readiness score out of 100 ✓ Permission audit: every declared permission cross-checked against your actual code (the number-one rejection cause) ✓ Remote-code detection: finds CDN scripts and remote imports that break Manifest V3 ✓ Manifest checks: missing files, missing icon sizes, broad host access, risky CSP ✓ A clear fix for every single finding, with the file it came from ✓ Optional store-listing check for keyword stuffing and promotional language ✓ Copy the full report to share with your team 🔓 WHAT PRO UNLOCKS ✦ Step-by-step fix guidance for every finding ✦ Listing and keyword optimizer that rewrites risky copy for you ✦ Full scan history so you can track a build across resubmissions ✦ Batch scan: check several builds or versions at once ✦ Export a clean report file 🎯 WHO IT IS FOR Solo developers and teams shipping a Chrome extension who do not want to burn a review cycle on an avoidable mistake. If you have ever been rejected and had no idea why, this Chrome extension checker is built for you. The Web Store now allows only one appeal, so the first submission has to count. 🛠️ HOW IT WORKS 1. Build your extension into a .zip (or grab the .crx). 2. Drop it onto CWS Submission Copilot. It unzips and analyzes everything in your browser. 3. Read the report: blockers first, then warnings, then everything that passed, each with a fix. 4. Fix the blockers, rescan, and submit with confidence. 💡 WHAT IT CATCHES → Permissions you declared but never use (Purple Potassium), the most common rejection → Remote or dynamic code that Manifest V3 forbids (Blue Argon) → Broad host access like all-urls that reviewers reject → Missing files, wrong-case paths and missing icon sizes that break the build → Keyword stuffing and promotional words like "best" or "free" in your listing (Yellow Argon, Red Nickel) → A missing privacy policy when your code touches user data 🔒 PRIVACY YOU CAN VERIFY This is the part that matters most for a developer tool. Your source code is sensitive, so CWS Submission Copilot never sends it anywhere. The package is unzipped and analyzed entirely inside your browser tab. The extension makes a few requests to our own server at peakproductivity.online: an anonymous license check, and anonymous, aggregate usage events (for example "installed" or "used a feature") labeled only with a random device id and the version number. These carry no personal data and never include the extension packages or their contents. If you choose to send feedback through the rating prompt, that message is sent too. There is no account and no broad host permission, so it cannot read the pages you visit. No third-party analytics, no data sold. 🛡️ SECURITY Built on Manifest V3 with no remote code. Everything it runs is bundled in the package and reviewed by the Chrome Web Store. It requests only storage and downloads. ❓ FREQUENTLY ASKED QUESTIONS Q: Does my code get uploaded? A: Never. The scan happens 100% in your browser. Your code, manifest and listing text never leave the tab. Q: Is a passing score a guarantee of approval? A: No. It is a readiness signal based on public Chrome Web Store policies. A clean scan removes the common, avoidable reasons for rejection, but the human review is still the final word. Q: What does it actually check? A: Manifest validity, Manifest V3, missing files and icons, broad host access, declared-but-unused permissions, remote and dynamic code, risky content security policy, cryptomining signatures, single-purpose risk, and optional store-listing problems. Q: Does it work on a .crx, not just a .zip? A: Yes. It reads both. For a .crx it strips the header and analyzes the embedded package. Q: Will it tell me how to fix each issue? A: Yes. Every finding includes the file it came from and a one-line fix. Pro adds step-by-step guidance and a listing optimizer. 🚀 GET STARTED Add CWS Submission Copilot, drop in your build, and see your readiness score in seconds. Catch the rejection reasons before Google's reviewers do, and ship your Chrome extension on the first try.