fiptcha 0.1.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,243 @@
+# Fiptcha
+
+Local, self-hosted CAPTCHA solving primitives for browser automation. Built for Figranium, designed to be usable by other Node.js browser automation projects.
+
+Fiptcha is the standalone CAPTCHA runtime extracted from Figranium. It contains the local model/runtime layer that Figranium uses to detect resources, manage vision models, solve image grids, interact with browser challenges, and optionally use an Apple Silicon MLX companion.
+
+Fiptcha does **not** require the Figranium application or task format. The package exposes its solver modules directly, so another application can integrate the pieces it needs around its own browser lifecycle.
+
+## Why Fiptcha?
+
+CAPTCHA solving inside a browser automation project tends to grow into its own subsystem: model selection, model downloads, resource checks, image-grid interpretation, challenge interception, browser interaction, platform-specific acceleration, and lifecycle management all need to work together. Fiptcha keeps that subsystem separate from the automation framework using it.
+
+The goals are:
+
+- keep local CAPTCHA solving self-hostable;
+- avoid coupling the solver to Figranium's UI, API, task schema, or storage layer;
+- expose reusable Node.js modules for other browser automation projects;
+- download model assets only when they are needed rather than bundling large weights;
+- select an appropriate local backend based on available resources;
+- support optional companion runtimes without making them mandatory for every installation.
+
+## Supported challenge families
+
+Fiptcha contains the local runtime used by Figranium for:
+
+- reCAPTCHA v2 image challenges;
+- hCaptcha image challenges;
+- Cloudflare Turnstile/browser challenge helpers.
+
+Support is intentionally described as challenge/runtime support rather than a guarantee that every CAPTCHA can be solved. Providers change their challenge implementations and may use additional risk signals beyond the visible challenge.
+
+## Features
+
+- Local CAPTCHA solving from a browser automation session.
+- Resource-aware model selection.
+- Verified, on-demand model downloads and model lifecycle management.
+- Image-grid classification and challenge handling.
+- Browser challenge interception helpers.
+- Companion-process client and runtime support.
+- Optional MLX acceleration for compatible Apple Silicon environments.
+- Container/resource probing utilities.
+- CAPTCHA benchmarking helpers.
+- Environment-variable configuration through the `CAPTCHA_*` settings used by the runtime.
+- Apache-2.0 licensing for reuse in other applications.
+
+## Requirements
+
+Fiptcha is a Node.js package and expects the host application to provide the browser/page object used for challenge interaction. It does not launch or manage your entire automation application for you.
+
+Model inference can require substantial memory. Fiptcha performs resource detection before selecting a local model. A provider-advertised 2 GB host is treated using decimal gigabyte semantics rather than incorrectly requiring a full 2 GiB/2048 MiB allocation.
+
+Large model files are not intended to be embedded into the npm package. They are fetched by the model-management layer when required.
+
+## Installation
+
+```bash
+npm install fiptcha
+```
+
+The package entry point is CommonJS, so it can be loaded with `require()` directly.
+
+```js
+const fiptcha = require('fiptcha');
+```
+
+## Basic usage
+
+The highest-level local solver can be used with a compatible browser page:
+
+```js
+const { solveLocalCaptcha } = require('fiptcha');
+
+const result = await solveLocalCaptcha(page, {
+  captchaType: 'recaptcha_v2',
+  timeout: 60_000
+});
+
+console.log(result);
+```
+
+Your application remains responsible for creating the browser, navigating to the target page, deciding when a solve should occur, and handling the solve result in its own workflow.
+
+## Integration model
+
+Fiptcha is designed as a runtime library rather than a complete automation framework. A typical integration looks like this:
+
+```text
+Your application
+    |
+    +-- browser lifecycle (Playwright/compatible host)
+    |
+    +-- challenge detection / solve trigger
+    |       |
+    |       +-- Fiptcha
+    |             +-- resource detection
+    |             +-- model manager
+    |             +-- model downloader
+    |             +-- local solver
+    |             +-- grid solver
+    |             +-- optional companion / MLX runtime
+    |
+    +-- application-specific result handling
+```
+
+This separation is deliberate. Fiptcha does not know about Figranium Tasks, blocks, Cabinets, executions, authentication, scheduling, or its UI.
+
+## Public API
+
+The root package currently re-exports the public functions from the following modules:
+
+- `captcha-local-solver` — high-level local solving logic;
+- `captcha-grid-solver` — image-grid solving primitives;
+- `captcha-interceptor` — browser/challenge interception helpers;
+- `captcha-resources` — host/container resource detection;
+- `captcha-model-manager` — model selection and lifecycle management;
+- `captcha-model-downloader` — model acquisition and verification;
+- `captcha-model-manifest` — model metadata;
+- `captcha-companion-client` — communication with the optional companion process;
+- `captcha-mlx-runtime` — MLX runtime integration;
+- `captcha-benchmark` — benchmark helpers.
+
+For example:
+
+```js
+const {
+  solveLocalCaptcha,
+  // Other model, resource, interception, and grid helpers are
+  // exported from the same package entry point.
+} = require('fiptcha');
+```
+
+Fiptcha is still young, so applications that depend on lower-level helpers should pin the package version while the standalone API is being stabilized.
+
+## Companion runtime
+
+Fiptcha includes the companion tooling that was previously embedded in Figranium.
+
+Install companion requirements:
+
+```bash
+npm run companion:install
+```
+
+Start the companion:
+
+```bash
+npm run companion:start
+```
+
+For the Docker-oriented path:
+
+```bash
+npm run companion:start:docker
+```
+
+The companion is optional. Applications that do not need that backend can use the ordinary Node.js runtime without making the companion part of their own product architecture.
+
+## Resource probing
+
+The package includes a probe command:
+
+```bash
+npm run probe
+```
+
+This is useful when validating the environment Fiptcha will run in, especially inside containers where reported memory limits may differ from the physical host.
+
+Resource detection is kept inside Fiptcha so applications embedding it do not need to reproduce Figranium-specific hardware checks.
+
+## Model management
+
+Fiptcha separates model metadata, downloading, resource selection, and inference/runtime behavior. This allows the package to choose a suitable backend without forcing every application to ship every supported model.
+
+The model downloader verifies model assets against the package's model manifest. Applications embedding Fiptcha should persist the configured model/cache directory if they do not want model assets to be downloaded again when an ephemeral container is recreated.
+
+## Configuration
+
+Fiptcha uses the `CAPTCHA_*` environment-variable configuration inherited from the standalone runtime extracted from Figranium. Configuration belongs to the process embedding Fiptcha; the package does not require a Figranium settings database.
+
+When integrating Fiptcha into another application, keep CAPTCHA/model configuration at the application boundary and pass browser state through the solver APIs rather than importing Figranium-specific configuration code.
+
+## Using Fiptcha outside Figranium
+
+Fiptcha is intentionally licensed and packaged for this use case. A third-party automation project can install `fiptcha`, provide its own browser page, call the high-level solver or lower-level exported helpers, and keep its own orchestration around the package.
+
+A good integration should generally:
+
+1. let the host application own browser creation and navigation;
+2. detect or decide when a CAPTCHA needs to be handled;
+3. invoke Fiptcha with the active page/challenge context;
+4. allow Fiptcha to manage its local model/runtime concerns;
+5. translate the returned result into the host application's own success/error model.
+
+Avoid copying Fiptcha source into the consuming project. Depending on the package keeps fixes to model handling, resource detection, and challenge logic independently upgradeable.
+
+## Figranium integration
+
+Figranium consumes Fiptcha as a dependency. Compatibility shims in Figranium preserve its previous internal CAPTCHA import paths while the implementation itself lives here.
+
+That means Fiptcha is not merely a separately published copy of the solver: this repository is intended to be the canonical implementation of the local CAPTCHA runtime used by Figranium.
+
+## Testing
+
+Run the package smoke tests with:
+
+```bash
+npm test
+```
+
+The test suite includes regression coverage for resource detection, including the 2 GB host threshold that previously rejected machines advertised as having 2 GB RAM because the check effectively required 2 GiB.
+
+## Current maturity
+
+Fiptcha began as an extraction of a production subsystem rather than a greenfield SDK. The underlying solver has already been exercised through Figranium, but the standalone package API is new.
+
+The high-level integration boundary is usable today. The main area that should be considered pre-stable is the exact shape and naming of lower-level exported helpers. Until a stable standalone API is declared, pinning an exact Fiptcha version is recommended for third-party applications.
+
+## Security and responsible use
+
+CAPTCHA systems are one part of a site's abuse-prevention and access-control strategy. Integrators are responsible for ensuring their automation is authorized and complies with applicable terms, policies, and law.
+
+Do not treat successful CAPTCHA handling as permission to access data or perform actions that the application is otherwise not authorized to perform.
+
+## Relationship to Figranium
+
+Fiptcha is part of the Figranium ecosystem but is independently reusable. Figranium provides the visual browser-automation product and orchestration layer; Fiptcha focuses on the CAPTCHA-solving runtime.
+
+## Contributing
+
+Bug reports and focused improvements are welcome. For solver bugs, include enough environment information to reproduce the issue, particularly:
+
+- operating system and architecture;
+- Node.js version;
+- container/runtime details if applicable;
+- available memory;
+- CAPTCHA provider/challenge family;
+- whether the ordinary runtime or companion/MLX path was used.
+
+Please avoid attaching sensitive cookies, credentials, or private browsing data to public issues.
+
+## License
+
+Fiptcha is licensed under the Apache License 2.0. See `LICENSE` for the full terms.

package/index.js

@@ -0,0 +1,12 @@
+module.exports = {
+  ...require('./src/captcha-benchmark'),
+  ...require('./src/captcha-companion-client'),
+  ...require('./src/captcha-grid-solver'),
+  ...require('./src/captcha-interceptor'),
+  ...require('./src/captcha-local-solver'),
+  ...require('./src/captcha-mlx-runtime'),
+  ...require('./src/captcha-model-downloader'),
+  ...require('./src/captcha-model-manager'),
+  ...require('./src/captcha-model-manifest'),
+  ...require('./src/captcha-resources')
+};

package/package.json

@@ -0,0 +1,32 @@
+{
+  "name": "fiptcha",
+  "version": "0.1.0",
+  "description": "Local CAPTCHA solving for browser automation. Built for Figranium, usable anywhere.",
+  "main": "index.js",
+  "license": "Apache-2.0",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/figranium/fiptcha.git"
+  },
+  "files": [
+    "index.js",
+    "src",
+    "scripts/captcha-mlx-worker.py",
+    "scripts/captcha-companion-requirements.txt",
+    "scripts/captcha-container-probe.js",
+    "scripts/install-captcha-companion.js",
+    "scripts/captcha-companion.js",
+    "README.md",
+    "LICENSE"
+  ],
+  "scripts": {
+    "companion:install": "node scripts/install-captcha-companion.js",
+    "companion:start": "node scripts/captcha-companion.js",
+    "companion:start:docker": "node scripts/captcha-companion.js --docker",
+    "probe": "node scripts/captcha-container-probe.js",
+    "test": "node tests/smoke.test.js"
+  },
+  "dependencies": {
+    "@huggingface/transformers": "^3.8.1"
+  }
+}

package/scripts/captcha-companion-requirements.txt

@@ -0,0 +1,8 @@
+mlx==0.30.6
+mlx-lm==0.30.6
+mlx-vlm==0.3.11
+transformers==5.1.0
+tokenizers==0.22.2
+huggingface-hub==1.4.1
+numpy==2.4.2
+Pillow==12.1.0