Why use custom HTTP signatures instead of just using Playwright?

[jsking-js]

I've been looking through the modules (like the X and GitHub ones) and noticed you're carefully mimicking browser headers and sec-ch hints manually using httpx.

As a random user just getting into OSINT tools:

• What is the benefit of this manual approach over just using a headless browser like Playwright or Selenium?
• Is it purely for performance/speed, or does it help with avoiding detection on certain targets?

I think a clear explanation of why the tool is built this way would be great for new contributors to understand the project's direction!

[kaifcodec]

"Great question! We chose httpx over Playwright for two main reasons:

1. Efficiency and Speed: OSINT requires scanning many sites quickly. A full browser like Playwright is resource-heavy and slow. Using httpx allows us to run concurrent checks in seconds, ensuring the tool stays fast and lightweight.

2. Surgical Control: Headless browsers often leave 'automation' fingerprints that sophisticated anti-bots detect. By manually mimicking headers, we have total control over the request signature. This makes the tool more portable and capable of running in environments where a full browser installation isn't possible."

Basically we want the tool to stay lightweight, fast and accurate.

[jsking-js]

That makes total sense. I didn't realize that headless browsers left such specific fingerprints (like the webdriver flags) compared to a clean HTTP client.

Thanks for your time @kaifcodec !