Security model
GeoHarness runs with a Cloudflare token that can change your zone, so its design keeps decisions pure, I/O narrow and every change attributable.
How is GeoHarness structured?
A pure Rust core, compiled to WebAssembly (wasm32-unknown-unknown, no WASI), makes every decision: twins, head tags, robots.txt, rewrite rules, the audit. It has no access to the filesystem, network, clock, environment or processes. A TypeScript host performs all I/O and asks the core what to do. The boundary is one contract with generated types.
What protects my site and account?
- Least privilege: the token needs only the permission groups of the features you enable, probed before any change.
- Tagged changes only: zone rules are matched by the
geoharness:<host>description prefix and guarded byhttp.host; other rules are preserved verbatim. - No shell: inputs reach the CLI as environment variables; build commands run as argument vectors and shell metacharacters are rejected.
- Secrets stay secret: the token is passed per process and redacted from streamed logs.
- Declared environment only: templates read only variables listed in
env; anything else is an error, never an empty string. - Contained output: every file the core produces is written inside the build output directory; paths that would escape it are refused.
- Pinned supply chain: actions are pinned by commit SHA; wrangler and Lighthouse CI are pinned by exact version; the shipped
dist/is rebuilt byte for byte in CI. - Dry runs for pull requests:
deploy: falseneeds no credentials and makes no Cloudflare call.
Is serving markdown to agents cloaking?
No. GeoHarness never varies content by user agent. Markdown is selected only by the request's Accept header, responses carry Vary: Accept, and the audit's equivalence check fails a twin that does not carry the page's words. Search crawlers get the same HTML as browsers.
What does this site send?
A strict Content Security Policy that allows one inline stylesheet by hash and nothing else inline, no scripts, no third-party requests, HSTS, nosniff and a same-origin opener policy.