Skip to content
B0904Public

About

Chrome Clone with add on's

Resources

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

CClone

Separate worlds. One browser.

Phase 0 validation

CClone is a proposed Chromium-derived browser built around isolated browsing identities called Containers. The product goal is to combine strong account separation, explicit per-container network routes, tracking resistance, and productivity features without overstating what those controls can guarantee.

Current status

Milestone 0: Discovery and feasibility — complete and CI-validated.

This repository does not yet contain a browser binary or Chromium source. It is not suitable for browsing, privacy-sensitive activity, or security evaluation. The first implementation milestone is blocked until a Chromium-capable Windows build host is provisioned; see the feasibility report.

CClone will never describe account separation, fingerprint resistance, proxying, or Tor routing as “complete anonymity.” Signing in to an identifying account, opening external files, installing extensions, or making operational mistakes can still reveal identity.

Phase 0 documents

Non-negotiable engineering rules

  1. Preserve Chromium sandboxing, Site Isolation, renderer separation, and the network-service security model.
  2. Keep downstream Chromium patches small, reviewable, inventoried, and continuously rebased.
  3. Treat the container boundary, route enforcement, updater, and extension policy as security boundaries.
  4. Fail closed for Tor containers. Never silently fall back to a direct route.
  5. Never move cookies, authentication, or storage between Direct and Tor identities.
  6. Do not claim a privacy or performance property without a reproducible test.
  7. Keep unfinished controls visibly experimental.

Repository strategy

The repository will hold CClone-owned code, build orchestration, tests, documentation, and a versioned downstream patch queue. It will not import the entire Chromium Git history. An exact upstream Chromium commit and dependency manifest must be pinned before the first engine patch is accepted.

Validation

Phase 0 validation has no third-party Python dependencies:

python scripts/validate_phase0.py

Licensing

No licence has yet been selected for original CClone code. Chromium and every redistributed dependency retain their own licences. See licensing status. Do not assume that publication of this repository grants a licence beyond rights provided by applicable law.

About

Chrome Clone with add on's

Resources

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages