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

@gitpagedocs/tools

v1.1.54

Published

Shared business-logic core for Git Page Docs (consumed by frontend, cli and mcp). Ships TypeScript source; consume via tsx or a TS-aware bundler.

Downloads

1,343

Readme

@gitpagedocs/tools

The shared business-logic core of the Git Page Docs monorepo — the single home for domain logic consumed by the frontend, the CLI, and the MCP server. It ships TypeScript source and is consumed via tsx (CLI/MCP) or a TS-aware bundler (Next transpilePackages).

Modules (src/)

| Module | Responsibility | |---|---| | ai/ | 14-provider AI system — data-driven PROVIDER_CATALOG, registry + factory (no switch chains), 5 family adapters (OpenAI-compatible, Anthropic, Gemini, Ollama, Cohere), SSE/NDJSON streaming, legacy↔catalog id mapping | | security/ | EncryptedCredentialVault (AES-256-GCM), SessionPasswordGate, plaintext migration; web + file storage adapters | | crypto/ | NodeCryptoService + WebCryptoService (SHA-256, PBKDF2, AES-256-GCM, masking, secure wipe); deriveDocAccessKeys / verifyDocAccess (double-hash documentation password gate shared by the CLI password command and the frontend gate) | | cache/ | MemoryCache, FileCache, WebStorageCache (Strategy over one Cache port) | | config/ | GitPageDocsConfigLoader (.json / .js / .ts) | | logger/ | Level-filtered logger with secret redaction | | errors/ | AppError + typed subclasses | | filesystem/ | FileService (root-bounded list/read/write/search) | | documentation/ | DocumentationService, patchManagedRegion, DocUpdater | | ports/ | Type-only contracts (logger, cache, crypto, security, config, ai) |

Entry points (exports)

. (full barrel) · ./ai · ./errors · ./ports · ./crypto/web · ./security/web · ./cache/web — the web subpaths are browser-safe (no node: imports) for the Next.js bundle.

Usage

import { createDefaultFactory, PROVIDER_CATALOG } from "@gitpagedocs/tools/ai";
import { EncryptedCredentialVault } from "@gitpagedocs/tools/security/web";

Tests

Unit + integration + E2E live in tools/tests/** (Vitest); self-tests in tools/smoke/**. Run from the repo root: npx vitest run and npm run smoke:all.