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

@sudobility/raidr_processor

v0.1.8

Published

Bundle format, redaction, and analysis for raidr web app capture

Readme

raidr_processor

The pure core of raidr — a bundle format, redaction engine, and analysis pipeline for capturing a running web app and reconstructing a working approximation of it.

npm install @sudobility/raidr_processor

What it does

raidr_processor holds everything about raidr that is a pure function. Given the raw material of a capture — requests, responses, chunks, source maps, DOM snapshots — it produces the derived artifacts that reconstruction needs:

| Area | Exports | |---|---| | Bundle format | createManifest, validateManifest, buildBundleFiles, zipBundle, contentPath | | Redaction | redactRequest, redactHeaders, redactJsonValue, redactHtmlHydration, createPseudonymizer | | Coverage | computeCoverage, toPathTemplate, endpointKey | | Analysis | parseSourceMap, recoverSources, inferSchema, buildApiModel, buildRouteModel, auditLinks, deriveTimeline | | Codegen | generateTypes, generateClient, generateReplayServer, generateProject |

The no-I/O constraint

This package performs no I/O. No fs, no path, no process, and no DOM in its tsconfig lib. That is not a style preference — it is what makes the package safe to bundle into a Chrome MV3 extension, and what keeps every one of these stages testable without fixtures on disk.

Callers supply bytes; raidr_processor returns values. The consumers below sit on opposite sides of that line and never see each other:

raidr_processor              pure: bundle format, redaction, coverage, inference, codegen
   ├── raidr_extension   browser: CDP capture, offscreen buffer, side panel
   ├── raidr_cli         bun:     unzip, filesystem, project emit, replay server
   └── raidr_crawler     bun:     headless crawl, bundle writing

Development

bun install
bun run typecheck
bun test
bun run build     # → dist/

Design spec and implementation plans live in docs/superpowers/.

The raidr project

| Repository | Role | |---|---| | raidr_processor | Bundle format and pure analysis — this repo | | raidr_extension | Chrome MV3 extension that performs the capture | | raidr_cli | Reconstruction CLI and the agent skill | | raidr_crawler | Headless crawler and the publish skill | | raidr_web | Landing site |

License

BUSL-1.1 — see LICENSE.md.