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

@forgeframe/proxy

v0.1.1

Published

Local localhost proxy -- scrub, inject, rehydrate, log

Readme

@forgeframe/proxy

Localhost proxy that scrubs sensitive data before it reaches a cloud LLM, then rehydrates the response on the way back. Your data stays on your machine. What leaves is tokenized. What comes back is logged.

Install

npm install @forgeframe/proxy

Usage

import { loadProxyConfig, startProxyServer, ScrubEngineImpl, TokenMapImpl, ProxyPipeline, ProxyProvenanceLogger, createUpstream } from '@forgeframe/proxy';
import { MemoryStore, MemoryRetriever } from '@forgeframe/memory';
import { MemoryInjectorImpl } from '@forgeframe/proxy';

const config = loadProxyConfig();
const scrubEngine = new ScrubEngineImpl(config);
const upstream = createUpstream(config);
const provenance = new ProxyProvenanceLogger(config.provenanceDbPath);

// Optional: wire memory for context injection
const store = new MemoryStore({ dbPath: config.memoryDbPath });
const memoryInjector = new MemoryInjectorImpl(new MemoryRetriever(store));

const pipeline = new ProxyPipeline({
  scrubEngine, memoryInjector, upstream, provenance, logger: config.logger,
});

await startProxyServer({ config, pipeline });
// Listening on 127.0.0.1:4740

Point your client at http://localhost:4740 instead of the cloud API. The proxy handles the rest.

Scrub pipeline

Three tiers, applied in sequence:

  1. Regex -- SSN, email, phone, IP, file paths. Deterministic, instant.
  2. Dictionary -- User-maintained blocklist/allowlist (JSON files). Instant.
  3. Local LLM -- Semantic detection via Ollama. 500ms timeout, fails open.

Scrubbed values become [FF:CATEGORY_N] tokens. The token map is bidirectional -- outbound tokenizes, inbound detokenizes.

Rehydration

  • Full responses: token map replaces all [FF:*] tokens in the response body.
  • Streaming: StreamRehydrator buffers partial tokens split across SSE chunk boundaries. Handles both Anthropic and OpenAI response formats.

Provenance

Every request logs: SHA-256 hash of original text, scrubbed body, redaction count, response hash, latency. Append-only JSONL. Raw PII is never stored in the log.

HTTP endpoints

  • GET /health -- { status: 'ok', proxy: 'forgeframe' }
  • POST /v1/messages -- Anthropic-compatible
  • POST /v1/chat/completions -- OpenAI-compatible

Limitations

  • LLM scrub tier is implemented but not yet wired to Ollama in production. Regex and dictionary tiers work standalone.
  • Needs integration testing against real cloud APIs.
  • Latency budget (<100ms overhead) not yet validated under load.

License

AGPL-3.0