Skip to content

v1.3.1 — Python front end, one shared stealth implementation

Choose a tag to compare

View all tags
@acunningham-ship-it acunningham-ship-it released this 26 Jul 18:06
v1.3.1
0d4f7d6

Published to npm as @achamm/veilbrowser@1.3.1. The Python front end ships in the companion release python-v1.3.1.

Added

  • A Python front end (python/) — see python-v1.3.1.
  • CHROME_FLAGS_LEAD / CHROME_FLAGS_TAIL and FINGERPRINT_STEALTH_BODY are now exported, so the launch flags and the injected stealth body have one definition shared by both front ends instead of a copy in each.

Fixed

  • The injected scripts are now pure ASCII, and a test enforces it. Bun's transpiler escapes non-ASCII to \uXXXX, which is value-preserving in a normal template but not in String.raw, where the raw text is the value. Measured: String.raw`a—b` is 3 characters under node and 8 under bun, with the literal characters \ u 2 0 1 4 ending up in the script served to the page. Veil runs under bun, so the em dashes in the stealth patch's comments were reaching pages as escape sequences.

    All seven occurrences were inside // comments, so nothing was broken — but one non-ASCII character inside a string value would have silently changed what the patch does, differently per runtime. Keeping these templates ASCII removes the class of bug, and it's what makes byte-parity with Python possible at all.

  • veilbrowser (Python) no longer needs websockets just to build a stealth script — the import moved into CDP.connect(), where it's actually used. This failed the 1.3.0 release in CI, so v1.3.0 was tagged but never published; npm goes 1.2.0 → 1.3.1.

Verified

  • 204/204 bun tests (197 before this release + 7 new parity tests)
  • 21/21 Python checks against a real Chrome, run from the installed wheel outside the source tree
  • node, bun and Python emit byte-identical stealth scripts for all four presets
Assets 2
Loading