Repository navigation
Releases
v1.0.2
v1.0.1
v1.0.0
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
-
The browser API is async and tab-free.
headless_chrome::Tabno longer appears in
any signature; a first-partyPagereplaces 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_blockingwrapping these calls — it is no longer needed, and
wrapping an async call in it is worse than useless. -
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. -
Errorgained aCdpvariant and is now#[non_exhaustive], so an exhaustive
matchon it needs a_arm. -
wreq-utilremoved, soEmulationvalues no longer reach this crate's API. Use
stealthscraper_rs::emulation::{chrome, safari_27, for_kind}instead. -
The
browserfeature no longer pullsheadless_chrome,tokio-tungstenite,
rand_distrorwreq-util. Code relying on those arriving transitively must depend on
them directly. -
MITM TLS moved to BoringSSL, so
rustls,tokio-rustls,rcgen,ringand
aws-lcare 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 (
cdpmodule):LaunchConfig/launch, aCdpTransportthat
demultiplexes replies byidand events bymethod, and a typedBrowserHandle/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
andProfilerare 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 (
emulationmodule): complete Chrome and Safari emulations —
TLS, HTTP/2 SETTINGS in wire order, connection window,HEADERSpriority, 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): aClientHelloparser 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 durableStateStorein the default build, needing no
dependency. Writes go to a sibling temp file, are flushed, thenrenamed over the target,
so a crash leaves either the previous complete file or the new one.- BoringSSL certificate authority (
camodule): 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-listrather
than having certificate checking disabled wholesale. impersonation_client(&BrowserProfile) -> wreq::ClientBuilderand apub 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 plusUser-Agent,Sec-CH-UA*andAccept-Languagefrom the same profile.
Re-exportingwreqmeans a consumer configuring the builder cannot end up on a different
wreqmajor from the one the emulation was measured against.pslas 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.ukis one and
example.comis 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:pslplus
psl-types, no further dependencies, MIT/Apache-2.0.cert_compressionmodule: brotli and zlib certificate-compression codecs (RFC 8879).
wreq5 took an enum of algorithms and supplied the codecs;wreq6 takes
&dyn CertificateCompressorand ships none. Thecompress_certificateextension is part
of theClientHello, so omitting it would change the JA4. No new dependencies —brotli
andflate2were 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. ACheck MSRVjob now runs
cargo check --all-features --all-targets --lockedon it, reading the version out of
Cargo.tomlso 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, andsolve_challenge,detect_challenge,rotate_profile
and everyhuman_*helper are nowasync.spawn_blockingis 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,
whichwreqalready links.rustls,tokio-rustls,rcgen,ring,aws-lc,
rustls-webpki,yasnaandpemare gone from the dependency graph: three
cryptographic backends became one. -
wreqnow builds withgzip/deflate/brotli/zstd, so theAccept-Encodingthe 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
fromboring2/tokio-boring2tobtls/tokio-btls— the successor bindings by the
same author, whichwreq 6links. Staying onboring2would have meant two vendored
BoringSSL builds in one binary. The move also resolves what would otherwise have shipped
as known issues:wreq 5.xis entirely yanked on crates.io, so a new consumer could
not have resolved the manifest andcargo updatecould not run at all, andlru 0.13
carried two unsoundness advisories (RUSTSEC-2026-0002, RUSTSEC-2026-0253). The graph
shrank from 151 to 140 crates (154 → 143 withbrowser).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.0is still a release cand...
v0.4.0
What's Changed
Full Changelog: v0.3.1...v0.4.0
v0.3.1
Release v0.2.0
Release v0.1.0
What's Changed
New Contributors
Full Changelog: https://github.com/YpNo/rs-cloudscraper/commits/v0.1.0