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

@razroo/iso-index

v0.1.0

Published

Deterministic local artifact index for AI-agent workflows: build, query, and verify where authoritative facts live without model calls.

Readme

@razroo/iso-index

Deterministic local artifact index for AI-agent workflows.

iso-index answers: where is the authoritative fact? It crawls configured local artifacts, extracts stable records, writes a compact JSON index, and lets agents query that index instead of repeatedly grepping or loading growing files into prompt context.

It is:

  • MCP-free: no tool schema or always-on prompt tokens.
  • Model-free: extraction is regex/table/JSONL/template based.
  • Domain-neutral: JobForge examples are included, but the package only knows about local files, records, keys, values, sources, and fields.

Install

npm install @razroo/iso-index

CLI

iso-index build --config index.json --root . --out .iso-index.json
iso-index query "example labs" --index .iso-index.json
iso-index has --index .iso-index.json --key "company-role:example-labs:staff-agent-engineer"
iso-index verify --index .iso-index.json
iso-index explain --config index.json

JobForge-Style Example

iso-index build \
  --config examples/jobforge-index.json \
  --root examples/jobforge-project \
  --out /tmp/jobforge.iso-index.json

iso-index query \
  --index /tmp/jobforge.iso-index.json \
  --key "company-role:example-labs:staff-agent-engineer"

iso-index has \
  --index /tmp/jobforge.iso-index.json \
  --kind jobforge.report.url \
  --key "url:https://example.test/jobs/123"

Config Shape

{
  "version": 1,
  "sources": [
    {
      "name": "reports",
      "include": ["reports/*.md"],
      "format": "text",
      "rules": [
        {
          "kind": "report.url",
          "pattern": "^\\*\\*URL:\\*\\*\\s*(?<url>https?://\\S+)",
          "key": "url:{url}",
          "value": "{source}",
          "fields": { "url": "{url}", "report": "{source}" },
          "tags": ["report", "url"]
        }
      ]
    }
  ]
}

Supported source formats:

  • text: line-by-line regex rules with named capture groups.
  • tsv: delimited rows with headers or explicit columns.
  • markdown-table: markdown table rows keyed by header names.
  • jsonl: one JSON object per line, flattened with dot paths.

Template placeholders support fields plus {source} and {line}. Filters:

  • {Company|slug}example-labs
  • {Status|lower}applied
  • {Role|trim} → trims whitespace
  • {field|json} → JSON stringifies the value

Library

import {
  buildIndex,
  hasIndexRecord,
  loadIndexConfig,
  queryIndex,
  verifyIndex,
} from "@razroo/iso-index";

const config = loadIndexConfig(JSON.parse(configText));
const index = buildIndex(config, { root: process.cwd() });
const matches = queryIndex(index, { text: "example labs" });
const alreadyApplied = hasIndexRecord(index, {
  key: "company-role:example-labs:staff-agent-engineer",
});
const verify = verifyIndex(index);

Boundary

iso-index does not decide which source is authoritative for your domain. It only builds and verifies a compact lookup layer from the sources you configure. Domain packages still own freshness rules, source precedence, and workflow decisions.