Skip to content

    Type a page, a command such as keryn scan, or a rule id.

    Supported environments

    View as Markdown

    Keryn scans locally. Browser scans need JavaScript, WebAssembly and module Web Workers. The CLI runs outside the browser and does not need browser storage.

    Browser Release policy Automated evidence
    Chrome Current and previous stable Playwright Chromium engine
    Edge Current and previous stable Playwright Chromium engine
    Firefox Current and previous stable Playwright Firefox engine
    Safari Current and previous stable on supported macOS/iOS Playwright WebKit engine; shipping Safari is not separately tested

    Engine tests are a compatibility signal, not proof that every branded browser release passed. The repository’s Supported environments workflow scans the same fixtures in Chromium, Firefox and WebKit and compares their finding fingerprints and core version with the CLI. It checks desktop (1363 × 936) and mobile (390 × 844) layouts and saves screenshots and a JSON receipt. CI uses the browser revisions pinned by the Playwright package lock; it does not download each browser’s previous stable release.

    Engine Version tested on Linux Risk fixture findings AI-BOM fixture findings
    Chromium 159.0.8154.6 14 16
    Firefox 159.0 14 16
    WebKit 27.2 14 16

    Every fingerprint set and core version matched the CLI at both viewport sizes. Denied IndexedDB access still allowed a fixture scan with Not saved and JSON export. These results describe the pinned engine run, not a separate certification of every branded browser release.

    Verified Chrome and Edge releases — 2026-11-19

    Section titled “Verified Chrome and Edge releases — 2026-11-19”
    Browser Releases tested on Linux x86-64
    Google Chrome 158.0.8127.36, 157.0.8103.78
    Microsoft Edge 157.0.4341.60, 156.0.4314.58

    Each release passed both CLI fixture comparisons and seven startup capability checks at desktop and mobile widths.

    Mozilla Firefox 160.0.1 and 159.0.1 each passed both production scan fixtures and seven startup capability checks on Linux x86-64 at 1363 × 936 and 390 × 844. The milestone and AI-BOM fixture fingerprints matched across both releases and widths. With IndexedDB denied, the app reported Not saved and exported the same milestone fingerprints as the in-browser result.

    Shipping Safari qualification remains pending.

    Use a device with at least 4 GB RAM for ordinary browser scans. This is a conservative operating recommendation, not a guarantee for arbitrarily large repositories. Start with small folders on devices below 4 GB; prefer the CLI for large scans. The browser warns when deviceMemory reports less than 4 GB. Browsers that do not expose that API are treated as unknown, not unsupported.

    IndexedDB is used for local saved analyses. Startup checks an actual write and, where available, the quota estimate. Less than 50 MiB of estimated free storage produces a warning. Quotas can change after startup: a completed scan is not proof that saving succeeded. Watch the analysis’s Not saved state and export results before closing the tab if saving fails.

    Private windows and restrictive browser policies can reduce storage or discard it when the window closes. A successful probe cannot promise persistence across private sessions. Export any result you need to keep.

    Missing capability What happens
    WebAssembly absent or invalid Unsupported: WebAssembly…; use the CLI or enable WebAssembly
    Worker API absent, blocked, or unable to start a module worker Unsupported: Web Workers…; use the CLI or a browser that permits workers
    IndexedDB unavailable or writes rejected Storage advisory; live results remain available, use exports; saving failures show Not saved
    Storage nearly full Quota advisory; export results and free browser storage
    Reported memory below 4 GB Small-folder advisory; large scans may exhaust memory

    The release tooling defines these six targets. Native qualification compares fixture results from the checkout, npm package and standalone executable. The table records which targets have passed.

    OS Architecture Release target Native fixture verification
    Linux (glibc) x86-64 linux-x64 Verified on Linux x64
    Linux (glibc) ARM64 linux-arm64 Pending a Linux ARM64 runner
    macOS Apple silicon darwin-arm64 Pending a macOS runner
    macOS Intel x86-64 darwin-x64 Pending a macOS runner
    Windows x86-64 win-x64 Pending a Windows x64 runner
    Windows ARM64 win-arm64 Pending a Windows ARM64 runner

    The npm CLI requires Node.js 22 or later. Standalone archives carry a Node runtime; Workbench commands also need the accompanying keryn-native executable from the same archive. Keep the archive contents together. Linux musl/Alpine and 32-bit systems are not included in this matrix. Start with 4 GB RAM for CLI scans too; memory requirements grow with the input and enabled engines.

    The 2026-11-17 platform work adds reproducible engine and capability-failure checks under monorepo issue #155. On the Linux build box, only Linux x86-64 executables can run natively; other targets require their own runners. Cross compilation alone is not recorded as execution proof. The generated matrix receipt records the exact browser versions, fixture counts and viewport results.