@prosopo/procaptcha-frictionless 2.8.31 → 2.11.1

package/CHANGELOG.md

@@ -1,5 +1,707 @@
 # @prosopo/procaptcha-frictionless
 
+## 2.11.1
+### Patch Changes
+
+- Updated dependencies [b03dad1]
+  - @prosopo/types@4.3.1
+  - @prosopo/api@3.4.9
+  - @prosopo/detector@3.4.37
+  - @prosopo/load-balancer@2.9.11
+  - @prosopo/procaptcha-common@2.10.18
+  - @prosopo/procaptcha-pow@2.9.5
+  - @prosopo/procaptcha-puzzle@2.10.9
+  - @prosopo/procaptcha-react@2.9.67
+
+## 2.11.0
+### Minor Changes
+
+- 2392aaf: Integrate the prosopo/dns sidecar against the procaptcha provider.
+  
+  - New admin endpoint `POST /v1/prosopo/provider/admin/dns/event` ingests batched DNS observation events from the sidecar (auth: admin sr25519 JWT) and merges resolver / peer IPs onto the matching Session record under a new `Session.dnsEvent` field.
+  - Frictionless response carries a per-session `dns_url` when the pronode has `DNS_EVENT_SUBZONE` + `DNS_EVENT_HMAC_SECRET` set. The HMAC path mirrors the sidecar's Rust implementation so both sides agree without shared per-request state.
+  - The frictionless bundle fires one no-cors GET to `dns_url` on detection completion (fire-and-forget; failures never affect the captcha flow).
+  - `dns_url` is included on the `reuse_session` short-circuit path too, not only the new-session path — otherwise repeat visits from the same user/IP/sitekey combination silently dropped the observation hop.
+  - Deploy compose entry for the sidecar plus a Caddy `layer4` SNI-passthrough block so the sidecar terminates TLS itself (no Cloudflare token needed). Caddy image must be rebuilt with the `caddy-l4` plugin.
+
+### Patch Changes
+
+- Updated dependencies [a1d60db]
+- Updated dependencies [2392aaf]
+  - @prosopo/types@4.3.0
+  - @prosopo/api@3.4.8
+  - @prosopo/common@3.1.38
+  - @prosopo/detector@3.4.36
+  - @prosopo/load-balancer@2.9.10
+  - @prosopo/procaptcha-common@2.10.17
+  - @prosopo/procaptcha-pow@2.9.4
+  - @prosopo/procaptcha-puzzle@2.10.8
+  - @prosopo/procaptcha-react@2.9.66
+
+## 2.10.3
+### Patch Changes
+
+- Updated dependencies [d3db08d]
+  - @prosopo/procaptcha-common@2.10.16
+  - @prosopo/procaptcha-react@2.9.65
+  - @prosopo/procaptcha-pow@2.9.3
+  - @prosopo/procaptcha-puzzle@2.10.7
+
+## 2.10.2
+### Patch Changes
+
+- 6c26669: Add per-site honeypot trap. When enabled, the provider attaches an encoded question (morse or semaphore, base64-wrapped) in the `x-prosopo-meta` response header on frictionless responses. The widget renders the value into an off-screen hidden input with `name="email_confirm"`; bots that auto-fill text inputs populate it and the value rides back on the solution submit as `clientMetaData.hp`, which is persisted on the `StoredCaptcha` record. Falls back to a random phrase from `PROSOPO_HONEYPOT_PHRASE_BANK_PATH` when no custom question is configured.
+- f7f9ec5: feat(provider,widget): reserved always-pass / always-fail test site keys
+  
+  Add two fixed, well-known reserved site keys (`ALWAYS_PASS_SITE_KEY` /
+  `ALWAYS_FAIL_SITE_KEY`) that force a deterministic captcha verdict for CI/CD and
+  integration testing, constant across production, staging and development.
+  
+  - `@prosopo/types`: shared constants + `getTestSiteKeyMode`, imported by both the
+    provider and the widget.
+  - `@prosopo/provider`: short-circuits the `submit*` and `verify` endpoints (verify
+    runs before the signature check, so no dapp secret is needed), serves an
+    invisible PoW session from the frictionless handler, and bypasses domain
+    middleware. Works in every environment with no DB record.
+  - `@prosopo/procaptcha-common` / `-react` / `-frictionless`: render a prominent
+    `TestModeBanner` warning (always pass/fail) plus a console warning so a test key
+    can never ship to production unnoticed.
+  
+  always-pass verifies at both the submit and verify layers; always-fail fails at
+  both. Safe in production by design: the override only weakens protection for a
+  dapp that deliberately opts in, mirroring reCAPTCHA's public test keys.
+- Updated dependencies [6c26669]
+- Updated dependencies [f7f9ec5]
+  - @prosopo/types@4.2.1
+  - @prosopo/api@3.4.7
+  - @prosopo/procaptcha-react@2.9.64
+  - @prosopo/procaptcha-pow@2.9.2
+  - @prosopo/procaptcha-puzzle@2.10.6
+  - @prosopo/procaptcha-common@2.10.15
+  - @prosopo/detector@3.4.35
+  - @prosopo/load-balancer@2.9.9
+
+## 2.10.1
+### Patch Changes
+
+- Updated dependencies [0fd81af]
+  - @prosopo/common@3.1.37
+  - @prosopo/load-balancer@2.9.8
+  - @prosopo/procaptcha-pow@2.9.1
+  - @prosopo/procaptcha-puzzle@2.10.5
+  - @prosopo/procaptcha-react@2.9.63
+  - @prosopo/procaptcha-common@2.10.14
+
+## 2.10.0
+### Minor Changes
+
+- 20cae63: feat(provider): re-route after PoW using decrypted behavioural data
+  
+  PoW solutions are now re-evaluated by the routing machine after submission.
+  Previously the routing decision was made up-front on a thin set of signals;
+  behavioural data only becomes available (decrypted server-side) once the
+  user submits their PoW solution, so a user with weak behavioural signals
+  could still earn a token by solving PoW alone.
+  
+  The submit endpoint now runs the routing machine a second time in a new
+  `postPow` phase, feeding in the decrypted behavioural data, the originating
+  session's score, request headers, JA4, and IP info. If the router escalates,
+  the provider mints a fresh session (carrying the original session's risk
+  profile) and returns `escalation: { captchaType, sessionId }` on the
+  `PowCaptchaSolutionResponse`. The `verified` flag is forced to `false` on
+  escalation — the user isn't done until they clear the follow-up.
+  
+  On the client, `ProcaptchaFrictionless` accepts the escalation via a new
+  internal `onEscalate` prop on the PoW widget and mounts the chosen image
+  or puzzle widget in place, splicing the new sessionId into the
+  `FrictionlessState`. The handoff is internal to the frictionless → pow
+  flow — dapps integrating Procaptcha see no API change.
+  
+  `RoutingMachineInputBase.phase` widens from `"route"` to
+  `"route" | "postPow"` so decision-machine configs can distinguish the two
+  passes.
+
+### Patch Changes
+
+- Updated dependencies [20cae63]
+- Updated dependencies [4d9923e]
+  - @prosopo/types@4.2.0
+  - @prosopo/procaptcha-pow@2.9.0
+  - @prosopo/api@3.4.6
+  - @prosopo/detector@3.4.34
+  - @prosopo/load-balancer@2.9.7
+  - @prosopo/procaptcha-common@2.10.13
+  - @prosopo/procaptcha-puzzle@2.10.4
+  - @prosopo/procaptcha-react@2.9.62
+
+## 2.9.6
+### Patch Changes
+
+- Updated dependencies [d351362]
+  - @prosopo/types@4.1.4
+  - @prosopo/api@3.4.5
+  - @prosopo/detector@3.4.33
+  - @prosopo/load-balancer@2.9.6
+  - @prosopo/procaptcha-common@2.10.12
+  - @prosopo/procaptcha-pow@2.8.62
+  - @prosopo/procaptcha-puzzle@2.10.3
+  - @prosopo/procaptcha-react@2.9.61
+
+## 2.9.5
+### Patch Changes
+
+- Updated dependencies [e2711ae]
+- Updated dependencies [5786629]
+  - @prosopo/types@4.1.3
+  - @prosopo/locale@3.2.4
+  - @prosopo/procaptcha-pow@2.8.61
+  - @prosopo/procaptcha-puzzle@2.10.2
+  - @prosopo/procaptcha-react@2.9.60
+  - @prosopo/api@3.4.4
+  - @prosopo/common@3.1.36
+  - @prosopo/detector@3.4.32
+  - @prosopo/load-balancer@2.9.5
+  - @prosopo/procaptcha-common@2.10.11
+
+## 2.9.4
+### Patch Changes
+
+- Updated dependencies [566c1f6]
+  - @prosopo/widget-skeleton@2.8.3
+  - @prosopo/procaptcha-pow@2.8.60
+  - @prosopo/procaptcha-puzzle@2.10.1
+  - @prosopo/procaptcha-react@2.9.59
+  - @prosopo/types@4.1.2
+  - @prosopo/procaptcha-common@2.10.10
+  - @prosopo/api@3.4.3
+  - @prosopo/detector@3.4.31
+  - @prosopo/load-balancer@2.9.4
+
+## 2.9.3
+### Patch Changes
+
+- 53bfd45: Detect when the widget is served over plain HTTP (an insecure browser context)
+  and show a clear "Procaptcha requires a secure (HTTPS) connection" message
+  instead of failing later with a cryptic `Provider Selection Failed` error.
+  Procaptcha depends on secure-context-only browser APIs (e.g. SubtleCrypto), so
+  the frictionless widget now short-circuits before the provider-selection retry
+  loop when `window.isSecureContext` is false. Adds the `WIDGET.INSECURE_CONTEXT`
+  translation key across all locales and an `isSecureBrowserContext` helper.
+- Updated dependencies [53bfd45]
+- Updated dependencies [91958da]
+  - @prosopo/procaptcha-common@2.10.9
+  - @prosopo/locale@3.2.3
+  - @prosopo/procaptcha-puzzle@2.10.0
+  - @prosopo/api@3.4.2
+  - @prosopo/types@4.1.1
+  - @prosopo/procaptcha-pow@2.8.59
+  - @prosopo/procaptcha-react@2.9.58
+  - @prosopo/common@3.1.35
+  - @prosopo/detector@3.4.30
+  - @prosopo/load-balancer@2.9.3
+
+## 2.9.2
+### Patch Changes
+
+- Updated dependencies [6a741ce]
+  - @prosopo/types@4.1.0
+  - @prosopo/api@3.4.1
+  - @prosopo/detector@3.4.29
+  - @prosopo/load-balancer@2.9.2
+  - @prosopo/procaptcha-common@2.10.8
+  - @prosopo/procaptcha-pow@2.8.58
+  - @prosopo/procaptcha-puzzle@2.9.2
+  - @prosopo/procaptcha-react@2.9.57
+
+## 2.9.1
+### Patch Changes
+
+- cc13a45: Defer the SIMD benchmark trigger to after the frictionless POST is in
+  flight, and stop attaching SIMD readings to the frictionless request
+  body. The previous `await detectionResult.getSimdReadings(0)` still
+  waited a microtask cycle and the full RSA-OAEP + AES-GCM encryption
+  (10–30ms) even when `timeoutMs` was `0`, and the benchmark itself —
+  a CPU-bound WASM loop — was running concurrently with the BotScore
+  worker, contending for cores on small VMs. Stretches like 344ms →
+  1167ms on staging were attributable to the contention.
+  
+  The first-hop-wins semantics on the provider mean we just lose the
+  frictionless-hop attach, not the signal — readings still attach on the
+  captcha challenge GET and on solution submit.
+  - @prosopo/procaptcha-common@2.10.7
+  - @prosopo/procaptcha-pow@2.8.57
+  - @prosopo/procaptcha-puzzle@2.9.1
+  - @prosopo/procaptcha-react@2.9.56
+
+## 2.9.0
+### Minor Changes
+
+- d865319: Add puzzle captcha (drag-to-target challenge) as a new captcha type:
+  provider endpoints, manager + widget package, types, demo pages, and
+  a `puzzleTolerance` site setting.
+
+### Patch Changes
+
+- 4aae4e6: Pull the frictionless POST critical path down by ~340ms on the test
+  hardware via four focused changes:
+  
+  - **Inline Signer.** `@polkadot/extension-base/page/Signer` is now a
+    static import in `ExtensionWeb2`. It's 0.5KB on disk but its dynamic
+    import was costing ~190ms of network round-trip; inlining removes
+    one separate chunk fetch + parse from the critical path.
+  
+  - **Pre-warm the CryptoWorker.** `CryptoWorkerManager` gains a public
+    `prewarm()` that actually spawns the Worker and lets its script
+    parse during chunk-load time. Previously the call at module load
+    only instantiated the manager class; the worker itself spun up
+    lazily on the first `runTask`, putting the ~500ms worker module-eval
+    inside the first `createAccount()` call. Now it overlaps with chunk
+    loading and is hot by the time it's needed.
+  
+  - **Prefetch providers at module load with an env-keyed cache.**
+    `prefetchProviders` and `getRandomActiveProvider` share an in-flight
+    `Promise<HardcodedProvider[]>` keyed by environment, so a module-load
+    prefetch and the later `customDetectBot` Promise.all reuse the same
+    network call. `procaptcha-frictionless` triggers the prefetch from
+    module-import time using `PROSOPO_DEFAULT_ENVIRONMENT` (browser-safe
+    `typeof process` guard + `EnvironmentTypesSchema.safeParse`), so the
+    HTTP fetch overlaps with chunk download instead of running as part
+    of the detection Promise.all.
+  
+  - **Lazy-load the three captcha solvers.** `ProcaptchaFrictionless`
+    no longer statically imports `Procaptcha`, `ProcaptchaPuzzle`, and
+    `ProcaptchaPow`; each is `await import(...)` at the point the
+    frictionless response picks a type. Two of the three wrappers used
+    to be dead weight in the initial bundle; now only the chosen solver
+    is downloaded, after the frictionless POST has fired. Pulls ~64KB
+    of solver UI (chosen wrapper + Emotion dev runtime + builder + lazy
+    shim) out of the initial captchaRenderer chunk.
+  
+  Combined with the earlier worker-related changes, the frictionless POST
+  on the puzzle-implicit test page is now ~1290ms vs ~1630ms before this
+  batch, and ~6500ms in the original baseline. The remaining floor is
+  dominated by the BotScoreWorker's obfuscated bundle parse + run.
+- 4aae4e6: Plumb the WASM SIMD CPU fingerprint readings (collected by the catcher
+  client per https://blog.azerpas.com/writing/wasm-simd-fingerprinting/)
+  through the captcha flow and onto the linked `Session` record.
+  Collection-only — no scoring or classification yet.
+  
+  The readings are sent at the earliest moment they're available so the
+  signal lands on the session as soon as possible:
+  
+  1. **Captcha-challenge GET** (PoW / Puzzle / Image) — the procaptcha
+     Manager calls `frictionlessState.getSimdReadings(0)` (non-blocking
+     cache check) and attaches it to the challenge-request body. The
+     provider handler decodes and patches the linked session via
+     `updateSessionRecord`.
+  2. **Solution submission** (PoW / Puzzle / Image) — same non-blocking
+     check on the submit body. Acts as a backup if the benchmark wasn't
+     ready in time for the challenge GET.
+  
+  Frictionless init itself stays SIMD-free (benchmark is too slow to gate
+  the first hop).
+  
+  Surface area:
+  
+  - `SimdReadings` discriminated union + `SimdOpReadingRecord` /
+    `SimdOpCategory` in `@prosopo/types`, plus `simdReadingsCodec` shared
+    encode/decode helpers so the browser SDK and the provider use the same
+    pipe-safe wire format.
+  - Optional `simdReadings: string()` on `CaptchaRequestBody`,
+    `GetPowCaptchaChallengeRequestBody`, `GetPuzzleCaptchaChallengeRequestBody`,
+    `CaptchaSolutionBody`, `SubmitPowCaptchaSolutionBody`, and
+    `SubmitPuzzleCaptchaSolutionBody`.
+  - `FrictionlessState.getSimdReadings` + `BotDetectionFunctionResult.getSimdReadings`
+    so the catcher's prefetched benchmark is consumed at the request sites.
+  - `ProcaptchaApiInterface.{getCaptchaChallenge, submitCaptchaSolution}` and
+    the `ProviderApi.{getCaptchaChallenge, getPowCaptchaChallenge, getPuzzleCaptchaChallenge,
+    submitCaptchaSolution, submitPowCaptchaSolution, submitPuzzleCaptchaSolution}`
+    client methods accept the field.
+  - Provider challenge + solution handlers decode via `decodeSimdReadings`
+    and `updateSessionRecord` (Mongoose `Mixed`, Zod discriminated-union
+    validation at the edge). The challenge-GET patch is fire-and-forget.
+  
+  Backward-compatible: older catcher clients omit the field at every layer;
+  the session record omits it in turn.
+- Updated dependencies [3c0be68]
+- Updated dependencies [f9ea09d]
+- Updated dependencies [4aae4e6]
+- Updated dependencies [4aae4e6]
+- Updated dependencies [d865319]
+- Updated dependencies [273926d]
+- Updated dependencies [753304b]
+- Updated dependencies [8bb7286]
+- Updated dependencies [f9ea09d]
+- Updated dependencies [4aae4e6]
+- Updated dependencies [4993813]
+- Updated dependencies [5f1ae53]
+  - @prosopo/types@4.0.0
+  - @prosopo/api@3.4.0
+  - @prosopo/load-balancer@2.9.1
+  - @prosopo/locale@3.2.2
+  - @prosopo/procaptcha-puzzle@2.9.0
+  - @prosopo/procaptcha-pow@2.8.56
+  - @prosopo/common@3.1.34
+  - @prosopo/widget-skeleton@2.8.2
+  - @prosopo/detector@3.4.28
+  - @prosopo/procaptcha-common@2.10.6
+  - @prosopo/procaptcha-react@2.9.55
+
+## 2.8.62
+### Patch Changes
+
+- 819ed95: Adding invisible mode to session data
+- Updated dependencies [819ed95]
+- Updated dependencies [33a6c57]
+  - @prosopo/types@3.16.1
+  - @prosopo/api@3.3.2
+  - @prosopo/load-balancer@2.9.0
+  - @prosopo/detector@3.4.27
+  - @prosopo/procaptcha-common@2.10.5
+  - @prosopo/procaptcha-pow@2.8.55
+  - @prosopo/procaptcha-react@2.9.54
+
+## 2.8.61
+### Patch Changes
+
+- Updated dependencies [f6a4402]
+- Updated dependencies [99dfb44]
+  - @prosopo/types@3.16.0
+  - @prosopo/api@3.3.1
+  - @prosopo/detector@3.4.26
+  - @prosopo/load-balancer@2.8.40
+  - @prosopo/procaptcha-common@2.10.4
+  - @prosopo/procaptcha-pow@2.8.54
+  - @prosopo/procaptcha-react@2.9.53
+
+## 2.8.60
+### Patch Changes
+
+- Updated dependencies [3e54c0a]
+  - @prosopo/types@3.15.0
+  - @prosopo/api@3.3.0
+  - @prosopo/detector@3.4.25
+  - @prosopo/load-balancer@2.8.39
+  - @prosopo/procaptcha-common@2.10.3
+  - @prosopo/procaptcha-pow@2.8.53
+  - @prosopo/procaptcha-react@2.9.52
+
+## 2.8.59
+### Patch Changes
+
+- Updated dependencies [946a8ba]
+- Updated dependencies [5614814]
+- Updated dependencies [b94890c]
+  - @prosopo/types@3.14.1
+  - @prosopo/locale@3.2.1
+  - @prosopo/api@3.2.11
+  - @prosopo/common@3.1.33
+  - @prosopo/detector@3.4.24
+  - @prosopo/load-balancer@2.8.38
+  - @prosopo/procaptcha-common@2.10.2
+  - @prosopo/procaptcha-pow@2.8.52
+  - @prosopo/procaptcha-react@2.9.51
+
+## 2.8.58
+### Patch Changes
+
+- Updated dependencies [06970d2]
+- Updated dependencies [fc514dd]
+- Updated dependencies [7be39c4]
+- Updated dependencies [42650db]
+- Updated dependencies [dd3e06e]
+  - @prosopo/procaptcha-common@2.10.1
+  - @prosopo/widget-skeleton@2.8.1
+  - @prosopo/locale@3.2.0
+  - @prosopo/types@3.14.0
+  - @prosopo/api@3.2.10
+  - @prosopo/procaptcha-pow@2.8.51
+  - @prosopo/procaptcha-react@2.9.50
+  - @prosopo/common@3.1.32
+  - @prosopo/detector@3.4.23
+  - @prosopo/load-balancer@2.8.37
+
+## 2.8.57
+### Patch Changes
+
+- Updated dependencies [73df23c]
+- Updated dependencies [8139819]
+- Updated dependencies [4a9c518]
+  - @prosopo/procaptcha-common@2.10.0
+  - @prosopo/widget-skeleton@2.8.0
+  - @prosopo/common@3.1.31
+  - @prosopo/procaptcha-pow@2.8.50
+  - @prosopo/procaptcha-react@2.9.49
+  - @prosopo/load-balancer@2.8.36
+
+## 2.8.56
+### Patch Changes
+
+  - @prosopo/procaptcha-pow@2.8.49
+  - @prosopo/procaptcha-react@2.9.48
+  - @prosopo/types@3.13.3
+  - @prosopo/procaptcha-common@2.9.41
+  - @prosopo/api@3.2.9
+  - @prosopo/detector@3.4.22
+  - @prosopo/load-balancer@2.8.35
+
+## 2.8.55
+### Patch Changes
+
+  - @prosopo/procaptcha-pow@2.8.48
+  - @prosopo/procaptcha-react@2.9.47
+  - @prosopo/types@3.13.2
+  - @prosopo/procaptcha-common@2.9.40
+  - @prosopo/api@3.2.8
+  - @prosopo/detector@3.4.21
+  - @prosopo/load-balancer@2.8.34
+
+## 2.8.54
+### Patch Changes
+
+- Updated dependencies [20192d2]
+  - @prosopo/widget-skeleton@2.7.14
+  - @prosopo/procaptcha-pow@2.8.47
+  - @prosopo/procaptcha-react@2.9.46
+  - @prosopo/types@3.13.1
+  - @prosopo/procaptcha-common@2.9.39
+  - @prosopo/api@3.2.7
+  - @prosopo/detector@3.4.20
+  - @prosopo/load-balancer@2.8.33
+
+## 2.8.53
+### Patch Changes
+
+- Updated dependencies [e6d9553]
+  - @prosopo/types@3.13.0
+  - @prosopo/procaptcha-pow@2.8.46
+  - @prosopo/procaptcha-react@2.9.45
+  - @prosopo/api@3.2.6
+  - @prosopo/detector@3.4.19
+  - @prosopo/load-balancer@2.8.32
+  - @prosopo/procaptcha-common@2.9.38
+
+## 2.8.52
+### Patch Changes
+
+- 730c61e: Speed up captcha
+- Updated dependencies [730c61e]
+- Updated dependencies [d5082a9]
+- Updated dependencies [e1ea65f]
+- Updated dependencies [c316257]
+  - @prosopo/load-balancer@2.8.31
+  - @prosopo/detector@3.4.18
+  - @prosopo/types@3.12.3
+  - @prosopo/procaptcha-common@2.9.37
+  - @prosopo/api@3.2.5
+  - @prosopo/procaptcha-pow@2.8.45
+  - @prosopo/procaptcha-react@2.9.44
+
+## 2.8.51
+### Patch Changes
+
+- Updated dependencies [dbcd098]
+- Updated dependencies [adb89a6]
+  - @prosopo/detector@3.4.17
+  - @prosopo/locale@3.1.29
+  - @prosopo/types@3.12.2
+  - @prosopo/api@3.2.4
+  - @prosopo/common@3.1.30
+  - @prosopo/procaptcha-pow@2.8.44
+  - @prosopo/procaptcha-react@2.9.43
+  - @prosopo/load-balancer@2.8.30
+  - @prosopo/procaptcha-common@2.9.36
+
+## 2.8.50
+### Patch Changes
+
+- Updated dependencies [f5c8725]
+  - @prosopo/detector@3.4.16
+
+## 2.8.49
+### Patch Changes
+
+- Updated dependencies [c5ee492]
+- Updated dependencies [a90eb54]
+  - @prosopo/common@3.1.29
+  - @prosopo/types@3.12.1
+  - @prosopo/load-balancer@2.8.29
+  - @prosopo/procaptcha-pow@2.8.43
+  - @prosopo/procaptcha-react@2.9.42
+  - @prosopo/api@3.2.3
+  - @prosopo/detector@3.4.15
+  - @prosopo/procaptcha-common@2.9.35
+
+## 2.8.48
+### Patch Changes
+
+- Updated dependencies [759d4e6]
+- Updated dependencies [676c5f2]
+- Updated dependencies [feaca02]
+  - @prosopo/detector@3.4.14
+  - @prosopo/load-balancer@2.8.28
+  - @prosopo/types@3.12.0
+  - @prosopo/procaptcha-common@2.9.34
+  - @prosopo/api@3.2.2
+  - @prosopo/procaptcha-pow@2.8.42
+  - @prosopo/procaptcha-react@2.9.41
+
+## 2.8.47
+### Patch Changes
+
+- Updated dependencies [8148587]
+  - @prosopo/detector@3.4.13
+  - @prosopo/types@3.11.1
+  - @prosopo/api@3.2.1
+  - @prosopo/load-balancer@2.8.27
+  - @prosopo/procaptcha-common@2.9.33
+  - @prosopo/procaptcha-pow@2.8.41
+  - @prosopo/procaptcha-react@2.9.40
+
+## 2.8.46
+### Patch Changes
+
+- Updated dependencies [5444635]
+  - @prosopo/detector@3.4.12
+
+## 2.8.45
+### Patch Changes
+
+- Updated dependencies [7f6ffc5]
+  - @prosopo/types@3.11.0
+  - @prosopo/api@3.2.0
+  - @prosopo/procaptcha-react@2.9.39
+  - @prosopo/detector@3.4.11
+  - @prosopo/load-balancer@2.8.26
+  - @prosopo/procaptcha-common@2.9.32
+  - @prosopo/procaptcha-pow@2.8.40
+
+## 2.8.44
+### Patch Changes
+
+- Updated dependencies [bca43e5]
+  - @prosopo/detector@3.4.10
+
+## 2.8.43
+### Patch Changes
+
+- Updated dependencies [ce4f831]
+- Updated dependencies [93fa086]
+- Updated dependencies [4de47f5]
+  - @prosopo/detector@3.4.9
+  - @prosopo/types@3.10.2
+  - @prosopo/api@3.1.49
+  - @prosopo/load-balancer@2.8.25
+  - @prosopo/procaptcha-common@2.9.31
+  - @prosopo/procaptcha-pow@2.8.39
+  - @prosopo/procaptcha-react@2.9.38
+
+## 2.8.42
+### Patch Changes
+
+- Updated dependencies [cde7550]
+  - @prosopo/types@3.10.1
+  - @prosopo/api@3.1.48
+  - @prosopo/detector@3.4.8
+  - @prosopo/load-balancer@2.8.24
+  - @prosopo/procaptcha-common@2.9.30
+  - @prosopo/procaptcha-pow@2.8.38
+  - @prosopo/procaptcha-react@2.9.37
+
+## 2.8.41
+### Patch Changes
+
+- Updated dependencies [ad6d622]
+  - @prosopo/types@3.10.0
+  - @prosopo/api@3.1.47
+  - @prosopo/detector@3.4.7
+  - @prosopo/load-balancer@2.8.23
+  - @prosopo/procaptcha-common@2.9.29
+  - @prosopo/procaptcha-pow@2.8.37
+  - @prosopo/procaptcha-react@2.9.36
+
+## 2.8.40
+### Patch Changes
+
+- Updated dependencies [ff58a70]
+- Updated dependencies [592adf1]
+  - @prosopo/types@3.9.0
+  - @prosopo/procaptcha-react@2.9.35
+  - @prosopo/procaptcha-pow@2.8.36
+  - @prosopo/api@3.1.46
+  - @prosopo/detector@3.4.6
+  - @prosopo/load-balancer@2.8.22
+  - @prosopo/procaptcha-common@2.9.28
+
+## 2.8.39
+### Patch Changes
+
+  - @prosopo/procaptcha-react@2.9.34
+
+## 2.8.38
+### Patch Changes
+
+- Updated dependencies [d2431cd]
+  - @prosopo/types@3.8.4
+  - @prosopo/api@3.1.45
+  - @prosopo/detector@3.4.5
+  - @prosopo/load-balancer@2.8.21
+  - @prosopo/procaptcha-common@2.9.27
+  - @prosopo/procaptcha-pow@2.8.35
+  - @prosopo/procaptcha-react@2.9.33
+
+## 2.8.37
+### Patch Changes
+
+  - @prosopo/procaptcha-react@2.9.32
+
+## 2.8.36
+### Patch Changes
+
+- Updated dependencies [bd6995b]
+  - @prosopo/detector@3.4.4
+  - @prosopo/types@3.8.3
+  - @prosopo/api@3.1.44
+  - @prosopo/load-balancer@2.8.20
+  - @prosopo/procaptcha-common@2.9.26
+  - @prosopo/procaptcha-pow@2.8.34
+  - @prosopo/procaptcha-react@2.9.31
+
+## 2.8.35
+### Patch Changes
+
+- Updated dependencies [9633e58]
+  - @prosopo/types@3.8.2
+  - @prosopo/api@3.1.43
+  - @prosopo/detector@3.4.3
+  - @prosopo/load-balancer@2.8.19
+  - @prosopo/procaptcha-common@2.9.25
+  - @prosopo/procaptcha-pow@2.8.33
+  - @prosopo/procaptcha-react@2.9.30
+
+## 2.8.34
+### Patch Changes
+
+- Updated dependencies [f52a5c1]
+  - @prosopo/types@3.8.1
+  - @prosopo/api@3.1.42
+  - @prosopo/detector@3.4.2
+  - @prosopo/load-balancer@2.8.18
+  - @prosopo/procaptcha-common@2.9.24
+  - @prosopo/procaptcha-pow@2.8.32
+  - @prosopo/procaptcha-react@2.9.29
+
+## 2.8.33
+### Patch Changes
+
+  - @prosopo/procaptcha-react@2.9.28
+
+## 2.8.32
+### Patch Changes
+
+- Updated dependencies [15254a3]
+  - @prosopo/detector@3.4.1
+
 ## 2.8.31
 ### Patch Changes
 

package/dist/ProcaptchaFrictionless.d.ts

@@ -1,3 +1,3 @@
 import { type ProcaptchaFrictionlessProps } from "@prosopo/types";
-export declare const ProcaptchaFrictionless: ({ config, callbacks, restart, i18n, detectBot, container, }: ProcaptchaFrictionlessProps) => import("react/jsx-runtime").JSX.Element | null;
+export declare const ProcaptchaFrictionless: ({ config, callbacks, restart, i18n, detectBot, container, }: ProcaptchaFrictionlessProps) => import("react/jsx-runtime").JSX.Element;
 //# sourceMappingURL=ProcaptchaFrictionless.d.ts.map