Browser source
Visit the Chromium project ↗Chromium, Blink & V8
Browser platform, web rendering and JavaScript execution form CAQA’s engine foundations. CAQA does not embed Mozilla’s Gecko engine.
ABOUT CAQA BROWSER
Shared foundations.
A distinct direction.
CAQA Browser brings a considered personal experience to Chromium foundations, with a focus on understandable controls, practical tools and honest release evidence.
OUR POINT OF VIEW
More purpose
in every window.
A browser is where research starts, everyday work gets done and ideas become something useful. CAQA’s direction is to make that space feel more intentional: a clear start page, connected tools and deliberate choices about access.
We build on open-source work and name those foundations. We also distinguish an implemented source feature from a tested release, and a public website from an approved desktop installer.
Developed by Sukh Sandhu
Explore the CAQA family ↗OPEN-SOURCE COMPONENTS
Credit where
it belongs.
Browser source
Project & licence ↗Mozilla Readability
Version 0.6.0 is inherited through Chromium’s reading components under Apache 2.0. Readability extracts article content; its presence is not universal Firefox add-on compatibility.
Update tooling
How TUF works ↗The Update Framework
TUF provides a foundation for signed metadata, expiry checks and rollback protection in the updater implementation. Protected production signing and release validation remain open gates.
Security tooling
OSV-Scanner project ↗OSV-Scanner
Dependency scanning covers selected updater and website dependency manifests. A scoped scan does not certify the Chromium engine, every extension or the complete browser.
Evaluated candidate
Explore the project ↗Brave adblock-rust
This filtering library has been considered for future integration. It is not an integrated CAQA component. CAQA’s existing filtering implementation is separate.
Project and marketplace names identify their respective owners. No partnership, endorsement or sponsorship is implied.
RESPONSIBLE DISTRIBUTION
Open code comes
with responsibilities.
Open-source components can avoid licence fees. Maintenance, hosting, signing and independent assessment still need resources.
Keep licence notices
Desktop Chromium credits are available at chrome://credits. Internal packages include Chromium and applicable filter-list notices; complete distribution licence review remains a release requirement.
Use components carefully
Content extracted from a web page remains untrusted. Reader integrations need safe output handling, and extension compatibility needs its own API and licence review.
Publish meaningful evidence
Security claims need repeatable tests, current upstream coverage and an assessment of the actual release artifact.
Read the evidence →MAKE A LITTLE ROOM FOR POSSIBILITY