env-supplement-proxy

What problem does it solve?

Browser-targeted obfuscated JavaScript (such as anti-scraping sign algorithms, data collection scripts) throws "X is not defined" errors when executed in headless Node environments, as Node lacks native browser global objects like window, navigator, and document. Manual stubbing of missing APIs is extremely slow, as developers cannot easily identify which specific properties the obfuscated script actually queries.

Core Features & Use Cases

• Recursive Proxy Auto-Disclosure: Wraps browser global objects in a recursive ES6 Proxy that automatically logs every accessed-but-undefined API path, so only the APIs actually used by the target script need to be supplemented.
• Iterative Auto-Completion Loop: Runs the target JS, catches missing API errors, supplies reasonable stubs (preferably values captured from real browsers), and reruns until output stabilizes, eliminating guesswork in environment setup.
• Anti-Detection Guidance & Framework Selection: Includes detailed guidance to bypass common anti-scraping environment checks (such as toString integrity, fingerprint consistency, and Proxy leakage) and a comparison table of 7 mainstream environment supplementation frameworks for different scenarios, from learning use cases to beating strong adversaries like Ruishu.
• Use Case: For example, if you have an obfuscated Android app sign algorithm that runs in the browser and uses navigator and window APIs, you can use this skill to run it headless in Node at high throughput without fully reversing the obfuscated code.

Quick Start

Use the env-supplement-proxy skill to automatically identify and fill missing browser environment APIs for the attached obfuscated JavaScript file so it executes correctly in a headless Node environment.