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

@backthread/redact

v0.1.2

Published

The one redaction fence — pure, zero-dependency string transforms that strip source code and tool I/O out of an AI coding-agent session transcript before anything leaves the machine. Keeps only natural-language rationale.

Readme

@backthread/redact

npm license

The one redaction fence used across Backthread. Pure, zero-dependency string transforms that strip source code and tool I/O out of an AI coding-agent session transcript before anything leaves the machine — keeping only the natural-language rationale.

The rule (load-bearing)

DROP every tool-use / tool-result record entirely. Keep only natural-language user prompts and assistant text/thinking. In the kept text, REDACT fenced code blocks (``` … ```) to a placeholder.

No source code and no tool I/O may leave this module — only derived rationale. This is defense-in-depth: redact at the boundary so a downstream bug can't exfiltrate code.

Install

npm install @backthread/redact

Requires Node.js ≥ 22.18. This package ships as source-only TypeScript (exports points at ./src/index.ts) and relies on Node's default type stripping. Zero runtime dependencies.

Usage

import { parseJsonl, redactTranscript, renderTranscript } from '@backthread/redact';

const records = parseJsonl(rawJsonlFromDisk);
const redacted = redactTranscript(records); // only prose survives; code → "[code redacted]"
const text = renderTranscript(redacted);

API

  • redactTranscript(records: unknown[]): RedactedTranscript — drop tool records, keep prose, redact code fences.
  • redactCodeFences(text: string): { text: string; count: number } — redact ``` fences in a single string.
  • renderTranscript(t: RedactedTranscript): string — render the surviving turns back to text.
  • parseJsonl(raw: string): unknown[] — parse a .jsonl transcript.
  • sessionTimestamp(records: unknown[]): string | null — first timestamp in a transcript.
  • CODE_REDACTION — the placeholder string substituted for each fenced code block.

License

MIT © Backthread