Skip to content

Releases

v1.0.2

Choose a tag to compare

@YpNo YpNo released this 06 Nov 09:15
575aecd

Other

  • (deps) update psl, log and brotli to current
  • add GitHub Sponsors and Ko-fi funding links

v1.0.1

Choose a tag to compare

@YpNo YpNo released this 24 Oct 07:20
6ccd603

Other

  • defer chromium-roots to the wreq release, and record why
  • (deps) consolidate the ten open Renovate updates

v1.0.0

Choose a tag to compare

@YpNo YpNo released this 26 Sep 12:10
ff42cbb

The headless-browser API is now fully async, headless_chrome is gone, and the only GPL
dependency is gone with it. Every fingerprint value the crate emits is now measured from a
real browser rather than transcribed or inferred.

This is a breaking release, and the first to commit to a stable API. The public enums
most likely to gain variants — Error, BrowserKind, ChallengeKind, ScraperEvent,
Action, Outcome, RotationStrategy, Ja4Error, EscalateReason, DemoteReason,
Transition — and the ClientHints struct are now #[non_exhaustive], so future additions
(Edge support, new challenge kinds, new events) will not require a 2.0. Enums closed by an
external specification (SameSite, Confidence, Transport) stay exhaustive.

⚠️ Breaking changes

  1. The browser API is async and tab-free. headless_chrome::Tab no longer appears in
    any signature; a first-party Page replaces it.

    0.4 1.0
    scraper.new_stealth_tab()? scraper.new_stealth_page().await?
    tab.navigate_to(url)?; tab.wait_until_navigated()?; page.navigate_and_wait(url, timeout).await?
    scraper.detect_challenge(&tab)? scraper.detect_challenge(&page).await?
    scraper.solve_challenge(&tab)? scraper.solve_challenge(&page).await?
    scraper.rotate_profile()? scraper.rotate_profile().await?
    CloudScraper::human_type_str(&tab, text)? CloudScraper::human_type_str(&page, text).await?
    CloudScraper::human_move_mouse(&tab, x, y)? CloudScraper::human_move_mouse(&page, x, y).await?
    GenericSolver::solve_cloudflare_turnstile(&tab)? GenericSolver::solve_cloudflare_turnstile(&page).await?

    Remove any spawn_blocking wrapping these calls — it is no longer needed, and
    wrapping an async call in it is worse than useless.

  2. BrowserProfile::random() now claims Chrome 153, not Chrome 124–126. This is a
    behavioural break with no compile error: code asserting on the User-Agent string, or
    pinned to a specific fingerprint, changes silently. The version is the one actually
    captured and the one the launched binary reports; the old profiles advertised a browser
    several years older than the one rendering the page, which feature detection alone
    exposes.

  3. Error gained a Cdp variant and is now #[non_exhaustive], so an exhaustive
    match on it needs a _ arm.

  4. wreq-util removed, so Emulation values no longer reach this crate's API. Use
    stealthscraper_rs::emulation::{chrome, safari_27, for_kind} instead.

  5. The browser feature no longer pulls headless_chrome, tokio-tungstenite,
    rand_distr or wreq-util.
    Code relying on those arriving transitively must depend on
    them directly.

  6. MITM TLS moved to BoringSSL, so rustls, tokio-rustls, rcgen, ring and
    aws-lc are gone from the graph. Only affects consumers that relied on them
    transitively; a consumer binary keeping rustls for its own clients is unaffected.

The pure domain modules (challenge, proxy_pool, geo, state, events) keep their
shape, so a no-features consumer only needs the #[non_exhaustive] note above.

Added

  • Own async CDP client (cdp module): LaunchConfig/launch, a CdpTransport that
    demultiplexes replies by id and events by method, and a typed BrowserHandle/Page
    surface of ~25 methods. Chrome is launched over --remote-debugging-pipe (no scannable
    TCP debug port) and without --enable-automation. Runtime, DOM, Log, Debugger
    and Profiler are never enabled — asserted by test, where the previous claim to that
    effect was false.
  • Dual-mode sessions (StealthSession, identity, http_scraper): solve the first
    challenge in a real browser, then carry the whole identity — profile, cookies (RFC 6265
    scoped), client hints, locale and the same egress proxy — onto a plain HTTP transport and
    shut the browser down. It re-escalates automatically on a fresh challenge or a
    near-expiry clearance cookie. Steady-state scraping runs with no Chrome process.
  • Measured emulation table (emulation module): complete Chrome and Safari emulations —
    TLS, HTTP/2 SETTINGS in wire order, connection window, HEADERS priority, pseudo-header
    order, and the header set and order — every value captured from the browser it claims to
    be.
  • JA4 measurement apparatus (ja4, tls_capture): a ClientHello parser and JA4
    computation, plus passive capture through the MITM proxy, so any browser's real
    fingerprint can be read off rather than guessed.
  • Capture tooling: examples/capture_fingerprint (TLS), examples/capture_h2 (HTTP/2
    frames, and header names as plaintext with --h1), examples/capture_hints (User-Agent
    Client Hints, including a console snippet for machines with no Rust toolchain), and
    examples/emulation_roundtrip (proves an entry reproduces its browser).
  • JsonStateStore: a durable StateStore in the default build, needing no
    dependency. Writes go to a sibling temp file, are flushed, then renamed over the target,
    so a crash leaves either the previous complete file or the new one.
  • BoringSSL certificate authority (ca module): one ephemeral in-memory CA per process,
    leaves minted on demand and cached per host, replacing a fresh self-signed certificate per
    CONNECT. The browser is pinned to it with --ignore-certificate-errors-spki-list rather
    than having certificate checking disabled wholesale.
  • impersonation_client(&BrowserProfile) -> wreq::ClientBuilder and a pub use wreq
    re-export, both in the default build. Many "protected" endpoints gate on the
    TLS/HTTP-2 fingerprint alone, with no JavaScript challenge; against those a browser is
    pure overhead and this is the two-line path. The builder already carries the measured
    emulation plus User-Agent, Sec-CH-UA* and Accept-Language from the same profile.
    Re-exporting wreq means a consumer configuring the builder cannot end up on a different
    wreq major from the one the emulation was measured against.
  • psl as a dependency, for the Public Suffix List that RFC 6265 cookie scoping needs.
    Which names are public suffixes is data, not a derivable rule — co.uk is one and
    example.com is not, and both have two labels — so a heuristic would be a guess of exactly
    the kind this crate's fingerprint values were rewritten to remove. It is a leaf: psl plus
    psl-types, no further dependencies, MIT/Apache-2.0.
  • cert_compression module: brotli and zlib certificate-compression codecs (RFC 8879).
    wreq 5 took an enum of algorithms and supplied the codecs; wreq 6 takes
    &dyn CertificateCompressor and ships none. The compress_certificate extension is part
    of the ClientHello, so omitting it would change the JA4. No new dependencies — brotli
    and flate2 were already in the graph — and decompression is bounded, because the peer
    controls the compressed bytes.
  • The declared MSRV is now verified. rust-version = "1.95" was a claim no job
    tested — every CI job pinned current stable — while being load-bearing enough to have
    ruled out a dependency upgrade during the advisory work. A Check MSRV job now runs
    cargo check --all-features --all-targets --locked on it, reading the version out of
    Cargo.toml so the job cannot drift from the claim. Verified against 1.95.0: it builds
    clean.
  • Automated stealth audit (tests/stealth_audit.rs, 14 live checks) and wire-level
    regression tests for TLS (ja4_egress), HTTP/2 (h2_egress) and headers
    (http_leg_headers).

Changed

  • Breaking: CloudScraper's browser API is async and tab-free. new_stealth_tab() →
    new_stealth_page().await, and solve_challenge, detect_challenge, rotate_profile
    and every human_* helper are now async. spawn_blocking is no longer needed or
    wanted.

  • Breaking: wreq-util (GPL-3.0) removed. Measured through the same harness, its newest
    Chrome entry put byte-identical TLS and HTTP/2 on the wire to values captured directly
    from the browser, so the GPL table bought nothing; the Safari entry it replaced was worse.
    The crate is now MIT + Apache-2.0 throughout.

  • Breaking: BrowserProfile::random() claims Chrome 153 — the version actually
    captured, and the version of the binary that renders the page. It previously claimed
    Chrome 124–126 while launching a much newer browser, which feature detection alone
    exposes.

  • MITM TLS termination and certificate minting moved from rustls + rcgen onto BoringSSL,
    which wreq already links. rustls, tokio-rustls, rcgen, ring, aws-lc,
    rustls-webpki, yasna and pem are gone from the dependency graph: three
    cryptographic backends became one.

  • wreq now builds with gzip/deflate/brotli/zstd, so the Accept-Encoding the crate
    advertises is one it can actually decode.

  • The impersonation client is wreq 6 (6.0.0-rc.31), and the TLS backend moved with it
    from boring2/tokio-boring2 to btls/tokio-btls — the successor bindings by the
    same author, which wreq 6 links. Staying on boring2 would have meant two vendored
    BoringSSL builds in one binary. The move also resolves what would otherwise have shipped
    as known issues: wreq 5.x is entirely yanked on crates.io, so a new consumer could
    not have resolved the manifest and cargo update could not run at all, and lru 0.13
    carried two unsoundness advisories (RUSTSEC-2026-0002, RUSTSEC-2026-0253). The graph
    shrank from 151 to 140 crates (154 → 143 with browser).

    All 13 fingerprint assertions pass unchanged — same JA4, same HTTP/2 SETTINGS, wire
    order, window, priority and pseudo-order, through an entirely different TLS stack. That is
    what the measurement apparatus was built for: the migration is verified rather than hoped.

    wreq 6.0 is still a release cand...

Read more

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 28 Jun 18:49
b521655

What's Changed

Full Changelog: v0.3.1...v0.4.0

v0.3.1

Choose a tag to compare

@github-actions github-actions released this 03 Jun 13:29
e30a465

What's Changed

  • feat: Create updates from June by @YpNo in #32

Full Changelog: v0.3.0...v0.3.1

Release v0.2.0

Choose a tag to compare

@github-actions github-actions released this 09 Mar 23:11
5d64538

What's Changed

  • feat: little improvements by @YpNo in #2

Full Changelog: v0.1.0...v0.2.0

Release v0.1.0

Choose a tag to compare

@github-actions github-actions released this 08 Mar 22:36
decec6d

What's Changed

  • feat: rs-cloudscraper init by @YpNo in #1

New Contributors

  • @YpNo made their first contribution in #1

Full Changelog: https://github.com/YpNo/rs-cloudscraper/commits/v0.1.0