Nothing to peek at.Nothing to slow down.
unpeek reads a 3-tier call graph before rewriting a token. 60fps loops and render bodies keep their original source; cold handlers enter a zero-escape O(1) vault and optional --aggressive Micro-VM.
- hot path
- left byte for byte
- cold path
- 92-char / 64-bit vault + Rivest MBA
- integrity
- order-free globalThis + host WASM
Default profile, measured by the benchmark suite in packages/unpeek/benchmarks.
The parser sees three execution tiers.
unpeek classifies your AST before rewriting a token: 60fps loops and direct UI component renders stay untouched, serialized Web Workers remain pristine, and nested handlers enter hardened cold paths.
Hot path (TRUE_HOT_60FPS & shallow render)
Loops, requestAnimationFrame, Three.js useFrame hooks, and direct component render bodies skip transformation cleanly. Nested async event handlers (onSubmit, handleSave) stay cold and protected.
Cold path & Tier 3 @unpeek-critical enclave
Auth checks, billing, API clients, and WebGPU shaders. Tier 2 applies a 92-char zero-escape O(1) vault, >=4-var semi-linear MBA + degree-3 Rivest QNR guards, and an in-place Uint8Array shader vault; Tier 3 / --aggressive adds a 43-opcode Micro-VM v2 and shared <1.2 KB host-coupled WASM KDF.
- 01ParseAcorn builds an AST for each client chunk. Server output is never opened.
- 02Classify3-tier graph separates TRUE_HOT_60FPS, SHALLOW_RENDER_COMPONENT, and SERIALIZED_WORKER.
- 03GuardCold paths receive >=4-var MBA, Rivest Z_2^32 QNR predicates, and neutral decoy bridges.
- 04Vault & VM92-char / 64-bit salted vault + Uint8Array shaders (--aggressive adds 43-op Micro-VM v2 + singleton WASM).
- 05SealOrder-independent globalThis shield attests integrity; multi-pass maps move to .unpeek-maps/.
Run the call graph yourself.
Same source, same seed. Turn the exemption off and watch the frame rate answer.
// license-guard.tsexport function renderFrame(t) { for (let i = 0; i < particles.length; i++) { particles[i].x += lerp(a, b, t); }} export function validateLicense(key) { const salt = "uNp33k_v4"; const url = "https://api.unpeek.dev/v1/license"; return check(key, salt, url);}Exempt: the loop runs as written.
Loop found. Flagged hot, then propagated to lerp and stepParticles.
Demo workload modeled on the project benchmark profile. Not a device benchmark.
What ships, and where it lands.
Every number below comes from the benchmark suite or the transform pipeline in this repository. Nothing is rounded up for the page.
- Gzip bundle delta
- +4% to +8% (Tier 1/2)
- src/core/protect.ts
- Client bundle scope
- static chunks only (workers isolated)
- src/core/detector.ts
Measured against legacy obfuscation.
The tradeoff is not speed against secrecy. It is where the secrecy is spent.
Both bars share one scale per row: the unpeek bar is the measured figure drawn against the legacy upper bound.
- String decode
- O(1) involutory / salted VM
- Legacy obfuscator: O(N) per call
- Source maps
- Vaulted, URL stripped
- Legacy obfuscator: Manual
- Integrity check
- Order-free globalThis + singleton WASM
- Legacy obfuscator: Regex self-defense
Legacy figures are published ranges for control-flow flattening presets. unpeek figures come from this repository's benchmark run.
The full manual lives on its own page.
CLI flags, bundler adapters, hot-path heuristics, the source map vault, the programmatic API and the security model. Every section is written against this repository.
Open the documentationOne line in postbuild.
unpeek reads the framework, finds the client output, and protects it. Server bundles stay readable.
No config file. No wrapper. Remove the postbuild line and the next build ships untouched.
$ npx unpeek init