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

@openweave/weave-link

v0.6.0

Published

WeaveLink — MCP Server for integrating WeaveGraph with AI clients

Readme

🧠 weave-graph

WeaveGraph — The knowledge graph engine at the heart of OpenWeave.

Part of the OpenWeave monorepo.


What it does

WeaveGraph manages all memory for an OpenWeave session:

  • Stores concepts, decisions, errors and corrections as typed graph nodes
  • Connects them with semantic edges (relates, causes, corrects, implements, depends_on)
  • Compresses context into the graph when the LLM window reaches 75% capacity
  • Retrieves relevant nodes from long-term memory given a query
  • Persists everything to disk by chat_id, survives across sessions

Node Types

| Type | Description | |---|---| | CONCEPT | A key idea or term in the project | | DECISION | An architectural or implementation decision | | MILESTONE | A planned deliverable | | ERROR | A response flagged as incorrect by the user (suppressed) | | CORRECTION | The correct version linked to an ERROR node | | CODE_ENTITY | A function, class, or module created during the session |

Edge Types

| Relation | Meaning | |---|---| | RELATES | General semantic relationship | | CAUSES | A causes B | | CORRECTS | A is the correction of B (B is an ERROR node) | | IMPLEMENTS | A implements B (code → decision) | | DEPENDS_ON | A depends on B | | BLOCKS | A blocks B |

Quick Start

from weave_graph import ContextGraphManager, NodeType, EdgeType

# Initialize for a session
graph = ContextGraphManager(chat_id="proj_abc123")

# Add a decision node
decision = graph.add_node(
    content="Use PostgreSQL for persistence, not SQLite — project will scale",
    node_type=NodeType.DECISION,
    tags=["database", "architecture"]
)

# Add a concept and relate it
concept = graph.add_node(
    content="Session persistence by chat_id",
    node_type=NodeType.CONCEPT
)
graph.add_edge(decision.id, concept.id, EdgeType.RELATES)

# Suppress an error and record correction
graph.suppress_error_node(
    node_id=bad_response_node.id,
    correction_content="Use async/await, not threading — the codebase is fully async"
)

# Query relevant context before responding
relevant = graph.query_relevant_nodes("database connection pooling", top_k=5)

# Compress context when window is getting full
compressed_summary = graph.compress_context_to_graph(
    context_text=long_conversation_text,
    llm_extractor_fn=my_extraction_function
)

Storage

All data is persisted to:

{storage_path}/{chat_id}/
├── context_graph.json    ← Full graph (nodes + edges)
├── roadmap.md            ← Human-readable milestone status
├── decisions.md          ← Decision log
└── errors.md             ← Error pattern registry

Installation

pip install openweave-graph
# or within the monorepo:
pnpm --filter weave-graph dev