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

@tirs/log-format

v0.2.11

Published

Tirs shared log wire format: the network/console transforms and redaction rules used by the Chrome extension, the Care SDK, and validated against the session viewer.

Readme

@tirs/log-format

Types, transforms, redaction and validators for the Tirs session log format — the network and console log files attached to a Tirs recording session.

Most integrations never need this package directly: the Tirs SDK produces these files for you. It exists for advanced cases — generating Tirs-compatible logs from your own capture pipeline, post-processing captured logs, or validating files before shipping them.

What it does

  • Transforms raw captured activity into the session log files: transformNetworkLog(entries, tabs, startTime, options?) and transformConsoleLog(entries, startTime, options?), including request classification (CSS / JS / Img / Fetch-XHR / …) and per-entry time offsets aligned to a recording's start.
  • Redacts sensitive values in place: redactNetworkLog(log), redactConsoleLog(log), redactText(text) — JWTs, bearer tokens, API keys, passwords, emails, credit cards (with checksum validation), IBANs, phone numbers, IPs, connection strings, private keys.
  • Validates structure: validateNetworkLog(x) / validateConsoleLog(x) return { valid, errors }; assertValidNetworkLog(x) throws with the error list.
  • Ships full TypeScript types for every shape (NetworkLogFile, ConsoleLogFile, RawNetworkActivity, RawConsoleEntry, TabMeta, …).

How to use

npm i @tirs/log-format
import {
  transformNetworkLog,
  redactNetworkLog,
  validateNetworkLog,
} from '@tirs/log-format';

const startTime = Date.now() - 60_000;

const log = transformNetworkLog(capturedEntries, [{ id: 1, url: location.href }], startTime);
redactNetworkLog(log);

const { valid, errors } = validateNetworkLog(log);
if (!valid) console.warn(errors);

Optional configuration

Both transforms take an optional third/fourth argument:

| Option | Type | Default | What it does | | --- | --- | --- | --- | | pausedMsBefore | (tsMs: number) => number | () => 0 | Paused wall-clock milliseconds accumulated before a given timestamp. Subtracted from each entry's time offset so logs stay aligned with a video that omits paused spans. Supply it if your recordings can be paused. | | creator | { name, version } | Tirs default | Stamped into the network log's creator field. Set it to identify your own capture pipeline. |

const options = {
  creator: { name: 'My Capture Pipeline', version: '2.0.0' },
  pausedMsBefore: (ts) => pauses
    .filter(p => p.end && p.end <= ts)
    .reduce((total, p) => total + (p.end - p.start), 0),
};

const network = transformNetworkLog(entries, tabs, startTime, options);
const console_ = transformConsoleLog(consoleEntries, startTime, options);

Redaction and validation take no options — the rule set is fixed so that output stays consistent across every producer of this format.

Zero dependencies; runs in browsers, workers and Node.

MIT © Tirs