THE CAQA MARKETPLACE

Your browser.
Your choice of tools.

Discover extensions across the Google, Mozilla and Microsoft marketplaces. Know what works with your browser before you choose.

Explore the marketplaces

OFFICIAL STORES

A wider world of extensions.

Opening a store does not install an extension.
Each store’s terms and privacy policy apply.

Find a tool

Showing 3 official marketplaces. Search terms are sent only when you open a store.

Chromium catalogue

Chrome Web Store

Explore Google’s extension catalogue for Chromium browsers, including CAQA’s browser engine family.

CAQA installation: not yet validatedAvailability depends on the extension, store and browser build. Review every permission prompt.

Browse Chrome Web Store

XPI compatibility preview

Firefox Add-ons

Explore Mozilla’s catalogue. CAQA is adding native import for Firefox WebExtensions that use compatible Manifest V3 features.

Compatible XPI import: validation pendingThe developer import is implemented in native source. Final build and runtime tests are pending. Firefox-only APIs and background pages still need a developer port.

Browse Firefox Add-ons

Edge catalogue

Microsoft Edge Add-ons

Explore Microsoft’s catalogue for the Edge browser, which also uses the Chromium engine.

Signed Chromium-format package importCompatible .crx packages use CAQA’s native installer and signature checks. End-to-end Edge catalogue installation and update tests are still pending.

Browse Edge Add-ons

NATIVE PACKAGE IMPORT

Bring compatible extensions into CAQA.

Desktop development preview: final build and runtime validation are pending. This website cannot install packages into your browser.

In a CAQA build containing the import feature, open Tools > Extensions (or enter chrome://extensions/ in the address bar).
For a compatible signed Chromium-format package from an Edge developer, drop its .crx file onto the Extensions page and review the native permission prompt.
For a compatible Firefox .xpi, enable Developer mode, then drop the file onto the Extensions page. Review the publisher-verification notice and required permissions before accepting.
In a validated build with CAQA’s new access controls, grant site access deliberately where the extension needs to work.

XPI imports currently require Manifest V3 and supported Chromium APIs, with a service worker if background code is needed. Mozilla signatures are not verified, updates are manual, and unverified XPI imports are disabled in protected workspaces. Import only developer code you trust.

A package import is separate from a store’s “Add to browser” button. CAQA does not claim universal Firefox compatibility or verified direct installation from Microsoft’s catalogue.

PERMISSION REVIEW

Understand what
an extension can ask for.

Have an extension’s manifest.json? Open it here to see its declared website access and sensitive permissions. The file stays in this page’s memory; it is not uploaded or saved.

This is a declaration review, not a security scan or compatibility test. It cannot inspect extension code, prove store authenticity, detect every API difference or approve installation.

Choose manifest.json

JSON only, up to 256 KB. ZIP, CRX and XPI packages are not opened.

Local review

Or paste manifest JSON

Manifest JSON

Choose a manifest to begin. Nothing is installed.

OPEN-SOURCE FOUNDATIONS

Built on shared work.
Clear about what is included.

In the browser source

Chromium, Blink & V8

The browser platform, web rendering and JavaScript engine. CAQA’s current engine is Chromium; Gecko is not embedded.

Chromium project ↗

In the browser source

Mozilla Readability

Version 0.6.0, inherited through Chromium’s reader components under Apache 2.0. It extracts article content. The separate XPI compatibility import uses Chromium’s WebExtensions runtime.

Mozilla project & licence ↗

In the update tooling

The Update Framework

Signed update metadata, expiry checks and rollback protection are implemented. Publisher signing and public installation tests remain release gates.

The Update Framework ↗

In the security tooling

OSV-Scanner

Checks selected updater and website dependencies. This scoped scan does not certify the Chromium engine or every extension.

OSV-Scanner project ↗

Brave’s adblock-rust is a reviewed candidate, not an integrated component. CAQA’s existing filtering implementation is separate. Third-party names identify their projects; no partnership or endorsement is implied.

THE CAQA DIFFERENCE

Built around your workspace.

Our development focus brings separate client profiles, explicit extension approval for protected workspaces, understandable site exceptions and published release evidence together.

These controls are implemented in development source. Full browser lifecycle tests and independent assessment remain pending. We publish the evidence and limits instead of an unverified “world’s first” or “most secure” claim.

Read the security evidence

For extension developers: can a Firefox extension be ported?

Often, but each extension needs a manifest, API, permission and licence review. Mozilla documents differences between WebExtensions implementations. CAQA’s native XPI import preview accepts compatible Manifest V3 packages without rewriting or re-signing them. It uses the existing browser.* API namespace. Developer mode and a native permission confirmation are required; Mozilla signature verification and Firefox automatic updates are not implemented. Final native build and runtime validation are pending.

Read Mozilla’s cross-browser guidance ↗