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

@browsercore/profiles

v0.2.0

Published

Browser fingerprint definitions (TLS / HTTP/2 / HTTP/1.1). Pure data — no protocol implementation.

Readme

@browsercore/profiles

npm version coverage lint

Browser fingerprint definitions (TLS / HTTP/2 / HTTP/1.1). Pure data — no protocol implementation lives here. Higher layers read these definitions and translate them into bytes, header order, and SETTINGS frames.

Responsibility

Define WHAT a browser fingerprint looks like: ordered cipher suites, TLS extension order, GREASE behavior, HTTP/2 SETTINGS, and HTTP/1.1 header order. Adding a new Chrome version means adding a new entry here — protocol implementations never change.

What it does NOT know about

  • TLS handshakes or cryptography
  • HTTP parsing or serialization
  • Sockets or I/O
  • Cookies

Install

npm install @browsercore/profiles

Quick usage

import { getProfile, listProfiles, registerProfile } from "@browsercore/profiles";
import type { ProfileId } from "@browsercore/profiles";

const chrome = getProfile("chrome-140" as ProfileId);
console.log(chrome.tls.cipherSuites); // ordered cipher list
console.log(chrome.http2.settings); // HTTP/2 SETTINGS frame values

const all = listProfiles(); // ["chrome-120", "chrome-128", ...] — insertion order

registerProfile(myCustomProfile); // extensibility hook

Public API

| Export | Kind | Purpose | | --- | --- | --- | | getProfile() | function | Look up a profile by id (throws UnknownProfileError if absent) | | listProfiles() | function | List every registered id, in insertion order | | registerProfile() | function | Register or overwrite a custom profile at runtime | | diffProfiles() | function | Field-by-field diff of two profiles, reporting each differing path | | DiffOptions | interface | Diff tuning (e.g. order-sensitive vs. multiset array comparison) | | ProfileDiff | interface | A single difference located by its dotted path | | buildExpectedClientHello() | function | Project a profile's TLS fields onto expected wire codes | | validateProfileAgainstCapture() | function | Validate a profile against a captured ClientHello | | ValidationResult | interface | { ok, diffs } outcome of validation | | TlsCapture | interface | A captured ClientHello parsed out of a packet capture | | ClientHelloExpected | interface | The wire values a profile's ClientHello should carry | | BrowserProfile | interface | Complete fingerprint across TLS + HTTP/2 + HTTP/1.1 | | TlsProfile | interface | Cipher order, extensions, GREASE, signature algorithms | | Http2Profile | interface | SETTINGS, window sizes, priority | | Http2Settings | interface | HTTP/2 numeric settings (RFC 9113 §6.5.1) | | Http2Priority | interface | Stream priority descriptor | | Http1Profile | interface | Default headers, header order, accept-encoding | | ProfileId | branded type | Opaque profile identifier ("chrome-140") | | ProfileName | literal union | "chrome" \| "firefox" \| "safari" \| "edge" | | ChromeProfiles / FirefoxProfiles / SafariProfiles / EdgeProfiles | const maps | Per-browser profile definitions | | assertNever() | function | Exhaustiveness check for switches over unions | | ProfileError | class | Base typed error (matched on kind) | | UnknownProfileError | class | Thrown when a profile id is not found | | ValidationError | class | Thrown on an unknown profile value or bad capture |

Shipped profiles

| Browser | Profiles | | --- | --- | | Chrome | chrome-120, chrome-128, chrome-140 | | Firefox | firefox-120, firefox-128, firefox-135 | | Safari | safari-17, safari-18 | | Edge | edge-120, edge-128 |

Dependency graph

@browsercore/profiles

No other @browsercore/* runtime packages and no Node built-ins are imported. This is a pure data package. @browsercore/dev is a dev-only dependency that supplies shared build / lint / test configuration (see Shared config).

Source layout

src/
├─ index.ts            Public API surface — re-exports from the rest of the package
├─ index.internal.ts   Barrel re-exporting the per-browser profile maps
├─ registry.ts         getProfile / listProfiles / registerProfile (Map-backed)
├─ diff.ts             diffProfiles — field-by-field diff of two profiles
├─ validate.ts         buildExpectedClientHello / validateProfileAgainstCapture
├─ codes.ts            IANA TLS registry codes (cipher suites, groups, versions, sig schemes)
├─ errors.ts           ProfileError / UnknownProfileError / ValidationError
├─ types.ts            BrowserProfile + per-layer profile interfaces
├─ utils.ts            assertNever / createId
└─ profiles/           Per-browser profile definitions
   ├─ chrome.ts        chrome-120, chrome-128, chrome-140
   ├─ firefox.ts       firefox-120, firefox-128, firefox-135
   ├─ safari.ts        safari-17, safari-18
   └─ edge.ts          edge-120, edge-128

Development

Requires Node >= 26. ESM only ("type": "module").

npm install      # installs @browsercore/dev (file:../dev) + siblings
npm run build    # tsc -p tsconfig.build.json (emit to dist/)
npm run typecheck
npm run lint     # oxlint --type-aware src/
npm test         # vitest run

Run a single test file:

npx vitest run tests/profiles.test.ts

Run tests by name pattern:

npx vitest run -t "returns a known Chrome profile by id"

Generate a coverage report:

npm test -- --coverage
node ../dev/bin/coverage-md.mjs   # writes COVERAGE.md + coverage/badge.json

Shared config

This package adopts @browsercore/dev, the shared config package for the @browsercore/* family. Configuration is centralized — this repo only wires it in:

| Concern | Mechanism | | --- | --- | | TypeScript strict flags | tsconfig.json extends @browsercore/dev/tsconfig.base.json | | Vitest config | vitest.config.ts calls definePackageConfig({ name: "profiles" }) | | Oxlint config | oxlint.config.ts extends @browsercore/dev/oxlint | | Coverage report | coverage-md bin from @browsercore/dev |

@browsercore/dev is declared as a devDependency via "@browsercore/dev": "file:../dev".

License

MIT