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

@watchmecode/ja4

v1.0.0

Published

Zero-dependency JA4 + JA4H fingerprinting for Node — own TLS ClientHello parser, validated byte-for-byte against read-tls-client-hello and the FoxIO reference.

Downloads

167

Readme

@watchmecode/ja4

Zero-dependency JA4 + JA4H fingerprinting for Node.js.

  • JA4 — TLS client fingerprint, computed from a raw ClientHello by an own, dependency-free parser (TLS record → handshake → ciphers/extensions, GREASE filtering). Validated byte-for-byte against read-tls-client-hello across real ClientHellos (SNI/ALPN variations and GREASE).
  • JA4H — HTTP client fingerprint, computed from the request line + headers. Validated against the FoxIO reference (e.g. curl → ge11nn030000_fe444ad14866_…).

JA4/JA4+ is a FoxIO standard. This library is an independent, MIT-licensed implementation with no runtime dependencies.

Install

npm install @watchmecode/ja4

JA4 — TLS fingerprint

Give it the raw ClientHello bytes (a TLS record starting 0x16, or a bare handshake message):

import { ja4FromBytes, parseClientHello, computeJa4 } from '@watchmecode/ja4';

const ja4 = ja4FromBytes(clientHelloBuffer);
// => "t13d1516h2_8daaf6152771_d8a2da3f94cd"

// or in two steps:
const hello = parseClientHello(clientHelloBuffer); // { cipherSuites, extensions, … }
const fp = computeJa4(hello);

Capturing the ClientHello off a socket is out of scope here (use read-tls-client-hello's readTlsClientHello, or your own peek); this library does the parsing + fingerprinting.

JA4H — HTTP fingerprint

import { computeJa4h } from '@watchmecode/ja4';

const ja4h = computeJa4h({
  method: 'GET',
  httpVersion: '1.1',           // '1.0' | '1.1' | '2.0'
  headerNames: ['Host', 'User-Agent', 'Accept'], // in on-the-wire order
  acceptLanguage: 'en-US,en;q=0.9',
  cookie: req.headers.cookie,   // raw Cookie header value, if any
});
// => "ge11nn03enus_8ddaef5d77af_000000000000_000000000000"

Header names keep their on-the-wire case (matches FoxIO for HTTP/1.1); under HTTP/2 servers normalize headers, so JA4H_b may differ there.

API

  • ja4FromBytes(bytes: Buffer): string
  • parseClientHello(bytes: Buffer): ParsedClientHello
  • computeJa4(hello: ParsedClientHello): string
  • computeJa4h(input: Ja4hInput): string
  • isGrease(value: number): boolean

License

MIT © Anton Weber