npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

anti-detect-browser

v1.2.4

Published

Windows-only anti-detect browser client SDK powered by the Engine runtime and Playwright CDP

Readme

anti-detect-browser

Engine-level anti-detect browser for Node.js — real device fingerprints, the standard Playwright API, zero learning curve.

Drive an undetectable Chromium with the Playwright API you already know. Fingerprints are applied at the engine level (not fragile JS patches), so canvas, WebGL, audio, fonts, WebRTC, timezone and locale are spoofed deep enough to satisfy the strictest detectors — while you keep writing plain page.goto(...).

import { AntiDetectBrowser } from 'anti-detect-browser'

const ab = new AntiDetectBrowser({ key: 'your-api-key' })
const { page } = await ab.launch({ profile: 'amazon-us', proxyId: 'your-proxy' })

await page.goto('https://example.com') // standard Playwright from here

Why anti-detect-browser

  • 🛡️ Engine-level spoofing — fingerprints are generated from real devices and applied inside the browser engine, not injected via JavaScript that detectors can unmask.
  • 🎭 Consistent identity — UA, platform, canvas, WebGL, audio, fonts, WebRTC, timezone and language all line up. No tells, no contradictions.
  • 🌍 Geo-aware — point a profile at a proxy and the browser's timezone, locale and WebRTC automatically follow the proxy's location.
  • 💾 Persistent profiles — each profile keeps its own cookies, storage and login state across runs, and syncs to the cloud.
  • 🔌 Standard Playwrightlaunch() returns a real Playwright Page / BrowserContext. Everything you know still works.
  • 🏷️ Account labels — floating tag, window title and theme color per profile, so you never act in the wrong account.
  • 📺 Live View — stream any session to your dashboard and share a watch link.
  • 🤖 MCP server — expose the browser to AI agents via the Model Context Protocol out of the box.

Detection benchmarks

Verified by launching a real profile through a US residential proxy (New York) with an engine-generated fingerprint, then opening the public detectors:

| Detector | Result | |----------|--------| | Whoer.net | 100% disguise — proxy not detected, no DNS leak, OS / browser / geo all consistent | | CreepJS | 0% headless, 0% stealth, confidence high, navigator.webdriver = false | | WebRTC | Exposes the proxy IP only — the real IP never leaks | | Timezone / Locale | Auto-aligned to the proxy: a US proxy IP yields a US timezone (e.g. America/New_York, America/Los_Angeles) + en-US "American English" | | Device coherence | UA Chrome 137, userAgentData (137.0.7151.69), platform, cores and memory all agree |

Results reflect one verification run; exact scores depend on the proxy and fingerprint. The point is consistency — every layer tells the same story.

Install

npm install anti-detect-browser playwright-core

Windows-only. The engine runtime and its fingerprint generation are Windows-native.

Quick start

import { AntiDetectBrowser } from 'anti-detect-browser'

const ab = new AntiDetectBrowser({ key: 'your-api-key' })

const { page } = await ab.launch({
  profile: 'amazon-us',                 // persistent profile (cookies, storage, login)
  proxy: 'http://user:pass@host:port',  // or proxyId for a managed proxy
})

await page.goto('https://example.com')

The engine applies the fingerprint at launch, so once launch() returns you have regular Playwright Page / BrowserContext objects with no extra setup.

Full options

const { browser, context, page } = await ab.launch({
  profile: 'my-account',     // persistent profile
  proxy: 'http://user:pass@host:port',
  proxyId: 'managed-proxy-id', // managed proxy; takes precedence over `proxy`
  label: '[email protected]',
  color: '#3366ff',
  headless: false,
  liveView: true,            // stream this session to your dashboard
})

await page.goto('https://example.com')
await browser.close()

MCP server

Run as an MCP server for AI agent integration:

{
  "mcpServers": {
    "anti-detect-browser": {
      "command": "npx",
      "args": ["anti-detect-browser", "--mcp"],
      "env": {
        "ANTI_DETECT_BROWSER_KEY": "your-api-key"
      }
    }
  }
}

Exposes tools such as launch_browser, close_browser, navigate and screenshot.

How it works

  1. Your API key authenticates an engine session with the server.
  2. The engine runtime is provisioned locally (cached after first use) and launched with a real-device fingerprint.
  3. The SDK connects over CDP and hands you a standard Playwright BrowserContext.
  4. Profiles persist locally and sync to the cloud; proxies set geolocation, timezone and language automatically.

Requirements

Documentation

Visit antibrow.com for full documentation.