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

sdtk-brain-kit

v0.2.2

Published

Standalone local-first second-brain vault CLI: immutable raw/ sources compiled into a markdown wiki/ knowledge layer, maintained by rails (ingest, compile, lint, search, graph viewer) while your agent is the knowledge engine.

Readme

sdtk-brain-kit

sdtk-brain is a standalone, local-first second-brain vault CLI. One job: turn a folder of immutable sources (raw/) into a compiled markdown knowledge layer (wiki/) that you — and your AI agent — can search, lint, and browse as a graph. The agent reading the vault (per its CLAUDE.md contract) is the knowledge engine; this CLI provides the deterministic rails only.

Package version in this source snapshot: 0.2.2 CLI command: sdtk-brain

Standalone by design: not part of the sdtk-kit umbrella, installs no agent skills, makes no network calls, needs no entitlement. It shares its graph builder and viewer with SDTK-WIKI at build time (byte-identity is CI-guarded).

Install

npm install -g sdtk-brain-kit
sdtk-brain --version

Quick start

mkdir my-vault && cd my-vault
sdtk-brain init                      # raw/ + wiki/ + workspace/ + CLAUDE.md
cp ~/some-article.md raw/inbox/
sdtk-brain ingest raw/inbox
sdtk-brain compile --mode safe --apply
sdtk-brain search "topic"
sdtk-brain open                      # docs view + graph view (local viewer, no server)

Commands

sdtk-brain init [--vault <path>]     scaffold a vault (refuses non-empty non-vault targets)
sdtk-brain ingest <file|dir>         semantic extraction over raw sources (report-first)
sdtk-brain compile --mode safe [--apply]   compile extraction into wiki/ pages
  --skip-conflicts (with --apply)          apply only the non-conflicting remainder;
                                           drifted pages stay untouched + reported
sdtk-brain search [--json] "<q>"     deterministic search over the vault wiki
sdtk-brain lint | maintain           report-first hygiene (orphans, links, stale, contradictions)
sdtk-brain discover --plan           gap-analysis plan
sdtk-brain enrich --source github --mode review   review-only external repo metadata
sdtk-brain open [--no-open]          build + open the graph viewer
sdtk-brain status                    vault status

There is deliberately no ask command: open the vault in your agent (or Obsidian) and ask there — grounded synthesis is the agent's job.

Vault layout

raw/        immutable sources (inbox, articles, papers, repos, notes, meetings, archive)
wiki/       compiled knowledge (sources, concepts, entities, comparisons, syntheses, …)
workspace/  scratch
CLAUDE.md   the agent operating contract
.brain/     machine state (reports, graph, provenance) — never edit by hand

Boundaries

  • 100% local: no LLM, no network, no telemetry, no entitlement
  • never mutates raw/ content; .brain/ is CLI-owned machine state
  • a vault is a standalone folder — init refuses non-empty non-vault targets