Browser extension and web app to view source code of Chrome, Firefox, Opera, and Edge extensions without installing them.
CRX Viewer is a browser extension and web application that enables developers to view the source code of Chrome, Firefox, Opera, and Edge extensions directly from their respective web stores without installation. It solves the problem of needing to install extensions just to inspect their code, making it easier to analyze, learn from, or audit extension functionality and security.
Browser extension developers, security researchers, and web developers who want to inspect, learn from, or audit the code of extensions available in public stores like Chrome Web Store or Firefox Add-ons.
Developers choose CRX Viewer because it provides a seamless, integrated way to view extension source code directly from store pages, with advanced features like regex search, syntax highlighting, and file hashing, all without requiring installation of the target extensions.
Add-on / web app to view the source code of Chrome / Firefox / Opera 15 extensions and zip files.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Adds buttons directly to Chrome, Firefox, Opera, Thunderbird, and Edge store pages, enabling one-click source viewing without manual download, as specified in the README's store list.
Features like regex search, syntax highlighting, and automatic beautification make code analysis efficient, with quick navigation between results and specific lines, per the README.
Allows downloading extensions as ZIP or CRX files, viewing embedded zips, and showing file hashes (MD5, SHA256, etc.), useful for offline analysis and security audits.
Works as a browser extension for multiple browsers and has an online demo for viewing any URL or ZIP file, ensuring broad accessibility.
Solely a viewer with no editing capabilities; users cannot modify or repackage extensions within the tool, requiring external software for development tasks.
Relies on the structure of official store pages for detection, so changes in store layouts or APIs could break functionality without updates.
Only displays static source code, lacking tools for inspecting extension behavior during execution, which limits use for dynamic debugging or performance profiling.