GeoHarness

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.

Updated · Report vulnerabilities as described in SECURITY.md.

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?

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.