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/care

v0.2.11

Published

Customer Care plugin for the Tirs capture runtime: turns captured console + network activity into the extension-compatible wire files.

Readme

@tirs/care

The Customer Care plugin for the Tirs capture runtime. It turns the raw console and network activity captured during a recording session into the log files attached to a Tirs session — applying PII redaction and time-aligning every entry with the recorded video.

What it does

  • Builds the session's network log (requests, responses, headers, bodies, timings, per-tab attribution) and console log (level, message, timestamp) when a recording stops.
  • Applies redaction before anything leaves the page: JWTs, bearer tokens, API keys, passwords, emails, credit cards (with checksum validation to avoid false positives), IBANs, phone numbers, connection strings, private keys and more. Entries that were redacted are flagged.
  • Reports honestly: if capture limits truncated anything, the output says how much was dropped.

How to use

npm i @tirs/core @tirs/care @tirs/recorder
import { init } from '@tirs/core';
import { care } from '@tirs/care';
import { mountRecorder } from '@tirs/recorder';

const tirs = init({ key: 'YOUR-KEY', plugins: [care()] });
mountRecorder(tirs);

That's the entire integration — the plugin runs automatically when a recording session ends.

Optional configuration

care() takes no options of its own. What it produces is shaped by the runtime options you pass to init(), so configure it there:

| Runtime option | Effect on the log files | | --- | --- | | redact | true (default) scrubs PII from both log files and flags the affected entries. | | denyUrls | Matching requests still appear in the network log, but their bodies are replaced with a placeholder. | | captureBodies | false produces a metadata-only network log — every request listed, no bodies. | | maxBodyBytes | Bodies above the cap are truncated and marked in place. | | preroll | Includes activity from before recording began; those entries carry negative time offsets relative to the video. |

init({
  key: 'YOUR-KEY',
  plugins: [care()],
  denyUrls: [/\/auth\//],   // keep credentials out of the network log
  preroll: 30_000,          // include the 30s before the customer hit record
});

See the @tirs/core page for the full option list and defaults.

If you use the framework packages (@tirs/react, @tirs/nextjs, @tirs/angular) or the script-tag install, this plugin is already included; you don't need to add it yourself.

MIT © Tirs