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

@gonk/scope

v0.0.20

Published

Five-tier scope abstraction for the gonk harness. Multi-root, symlink-aware, with blob storage and ambient-document scanning.

Readme

@gonk/scope

Five-tier scope abstraction for the gonk harness. Multi-root, symlink-aware, with blob storage and ambient-document scanning.

Tiers

session > directory > project > persona > global

Resolution walks most → least specific when the tier isn't specified.

Roots within a tier

Each tier has a home directory. Inside the home, multiple known roots are scanned in broad → narrow order; last-found wins:

agents/, .agents/  →  .pi/  →  .claude/  →  .codex/  →  .gemini/  →  .cursor/
.windsurf/  →  .opencode/  →  .aider/  →  .gonk/

Symlinks are resolved via realpath and deduped by canonical path.

Ambient documents

Auto-scans for AGENTS.md (case-insensitive), CLAUDE.md, GEMINI.md, SOUL.md, PERSONA.md, AGENT.md, .cursorrules at every scope home and within bound roots. SOUL.md / PERSONA.md / AGENT.md are persona-bearing; the rest are context-bearing.

Entry points

// Full bundle
import { FsScopeStore, MemoryScopeStore } from "@gonk/scope";

// Types only — zero runtime cost
import type { ScopeStore, ScopeName } from "@gonk/scope/types";

// Just the in-memory store (testing) — no node:fs / yaml deps
import { MemoryScopeStore } from "@gonk/scope/memory";

// Filesystem store + standard root adapter
import { FsScopeStore, StandardRootAdapter } from "@gonk/scope/fs";

// Just the discovery helpers
import { findProjectRoot, scanDocuments, bindRoots } from "@gonk/scope/resolver";

Quick example

import { FsScopeStore } from "@gonk/scope/fs";

const scope = new FsScopeStore({ cwd: process.cwd() });

// Read with chain walk (returns most-specific match)
const provider = scope.get("tts.provider");

// Inspect the full chain
const all = scope.resolve("tts.provider");
// → [{ scope: "session", root: "...", value: "..." }, ...]

// Set explicitly
scope.set("tts.provider", "mlx-cloning", "persona", { kind: ".claude" });

// Documents
const docs = scope.documents();   // ambient AGENTS.md, CLAUDE.md, etc.