unreleased

unreleased / hellojs

Public

Node.js HTTP client whose TLS/H2/H3 handshake produces the same JA4/Akamai/peetprint fingerprint as a real Chrome browser. Drop-in request-shape API.

16
4
50% credibility
Found May 17, 2026 at 16 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
JavaScript
AI Summary

@unreleased/hellojs is a Node.js HTTP client library that makes outgoing requests appear to websites as if they're coming from a real Chrome browser. It achieves this by precisely matching Chrome 147's TLS handshake patterns, HTTP/2 settings, and other connection fingerprints that bot-detection systems analyze. The library functions as a drop-in replacement for familiar HTTP clients like 'request', supporting HTTP/1.1, HTTP/2, and HTTP/3, along with features like connection pooling, cookie handling, proxy support (HTTP CONNECT and SOCKS5), session resumption, and 0-RTT early data. By default it validates server certificates properly. Users can either use the built-in Chrome 147 fingerprint profile or import custom fingerprints from tls.peet.ws captures to mimic other browsers.

How It Works

1
🔍 Discovering a fingerprinting problem

You build automation with Node.js but notice your requests get blocked or challenged, even when you try to hide your user-agent.

2
🤔 Learning about browser fingerprints

You discover that websites don't just check your user-agent—they analyze the exact shape of your TLS handshake, HTTP settings, and connection patterns to identify 'bots'.

3
🔧 Finding a library that speaks Chrome

hellojs lets your Node.js code talk to websites using the exact same fingerprint as a real Chrome browser on macOS—including cipher lists, extension order, and connection settings.

4
📦 Installing and making your first request

You install the package and make a request the same way you'd use any other HTTP library, but now the website sees you as Chrome.

5
Choosing your connection path
🔄
Automatic mode

hellojs upgrades to HTTP/3 when the server supports it, falls back gracefully when it doesn't

🔒
Proxy support

Route traffic through HTTP CONNECT or SOCKS5 proxies while keeping the Chrome fingerprint intact

6
🍪 Managing cookies like a real browser

Your requests automatically handle cookies, respecting expiration dates, secure flags, and domain matching—just like Chrome does.

🎉 Your automation works undetected

Your requests pass through bot detection systems because they look exactly like real Chrome browser traffic—no more challenges or blocks.

Sign up to see the full architecture

5 more

Sign Up Free

Star Growth

See how this repo grew from 16 to 16 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is hellojs?

hellojs is a Node.js HTTP client that mimics Chrome's browser fingerprint at the TLS and HTTP protocol layers. When you make requests with this library, your traffic looks identical to Chrome 147 on macOS -- same cipher suites, same extension order, same HTTP/2 settings, same GREASE values. It exposes a drop-in API compatible with the popular `request` library, so you get familiar patterns like `request.get()`, `request.post()`, JSON body handling, cookies, and streaming without rewriting your existing code. Under the hood it speaks HTTP/1.1, HTTP/2, and HTTP/3 (QUIC) with full connection pooling and proxy support.

Why is it gaining traction?

The hook is simple: bot detection services like Cloudflare, Akamai, and DataDome can identify Node.js traffic from its TLS fingerprint alone -- no amount of User-Agent spoofing helps. hellojs solves this by producing the exact same JA4, Akamai, and peetprint hashes as a real browser. It also includes a "Parrot" feature where you can paste any fingerprint captured from tls.peet.ws and have hellojs clone it. Performance benchmarks show it trails native HTTP/2 by only a few milliseconds on warm connections while being significantly faster than other Node HTTP clients under concurrent load.

Who should use this?

This is for developers building web scrapers, API clients, or automation tools that need to blend in with normal browser traffic. Security researchers testing fingerprinting defenses will find it useful for generating realistic-looking Node traffic. Anyone running services behind bot management products who needs to make HTTP requests from a Node environment without triggering false positives. Note that this is early-stage software with 16 stars -- expect rough edges and evolving APIs.

Verdict

hellojs solves a real problem that no other Node library addresses, but its 0.5% credibility score reflects real maturity concerns. The documentation is thorough and the feature set is impressive for a project this young, but you should treat it as experimental until it gains more community traction. Worth evaluating for specific use cases, but maybe not ready for production systems without careful testing.

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.