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

@blackwell-systems/knowing

v0.15.1

Published

Content-addressed knowledge graph for software systems

Downloads

1,007

Readme

@blackwell-systems/knowing

Self-adapting code intelligence engine. Gives AI agents ranked, graph-aware context instead of grep results. Gets smarter with scale, not dumber.

Install and verify

npm install -g @blackwell-systems/knowing
knowing version   # should print the version

Configure your agent

Add to your agent's MCP config (.mcp.json for Claude Code, .cursor/mcp.json for Cursor, .vscode/mcp.json for VS Code, see all):

{
  "mcpServers": {
    "knowing": {
      "command": "knowing",
      "args": ["mcp", "--watch"],
      "transport": "stdio"
    }
  }
}

The MCP server auto-indexes your repo on first launch (10-30 seconds). No model downloads, no API keys required.

First useful query

Ask your agent:

"Use the context_for_task tool to find symbols related to [something you know exists in your code]."

You should see ranked symbols with scores and file paths. If results are empty, the repo is still indexing. If results seem unrelated, use specific symbol names in your task description.

What it does

knowing indexes code across 23 extractors (Go, TypeScript, Python, Rust, Java, C#, and more) into a content-addressed knowledge graph. 38 edge types, 28 MCP tools, 277 equivalence classes bridging task vocabulary to code symbols.

P@10 = 0.330 across 302 tasks, 17 repos, 8 languages. 13 self-adapting mechanisms. 3.79x codegraph, 6.00x GitNexus.

CLI usage

knowing add .                                          # index a repo
knowing context -task "refactor auth" -format gcf      # ranked context
knowing test-scope -files internal/auth/handler.go     # affected tests
knowing why -task "refactor auth" -symbol "SessionHandler"  # explain ranking
knowing enrich lsp                                     # LSP enrichment for higher-quality edges

Documentation

Full docs at https://blackwell-systems.github.io/knowing

Source: https://github.com/blackwell-systems/knowing