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

@oraclaw/graph

v1.0.0

Published

Find the decisions that matter most. PageRank, community detection, and critical path analysis for any network.

Downloads

52

Readme

@oraclaw/graph

Find the decisions that matter most. PageRank for your projects. Community detection for your dependencies. Critical path through your roadmap.

Feed in any network of connected things — tasks, decisions, features, people — and get back: what's most influential, what clusters together, and what's the bottleneck.

Quick Start

npm install @oraclaw/graph
import { OraGraph } from "@oraclaw/graph";

const graph = new OraGraph({ apiKey: "ok_live_..." });

const analysis = await graph.analyze(
  [
    { id: "auth", type: "action", label: "Build Auth System", urgency: "critical", confidence: 0.8, impact: 0.9, timestamp: Date.now() },
    { id: "payments", type: "action", label: "Stripe Integration", urgency: "high", confidence: 0.6, impact: 0.8, timestamp: Date.now() },
    { id: "launch", type: "goal", label: "Public Launch", urgency: "critical", confidence: 0.5, impact: 1.0, timestamp: Date.now() },
    { id: "onboarding", type: "action", label: "User Onboarding Flow", urgency: "medium", confidence: 0.7, impact: 0.6, timestamp: Date.now() },
    { id: "monitoring", type: "action", label: "Error Monitoring", urgency: "low", confidence: 0.9, impact: 0.4, timestamp: Date.now() },
  ],
  [
    { source: "auth", target: "payments", type: "enables", weight: 0.9 },
    { source: "auth", target: "onboarding", type: "enables", weight: 0.8 },
    { source: "payments", target: "launch", type: "enables", weight: 0.9 },
    { source: "onboarding", target: "launch", type: "enables", weight: 0.7 },
    { source: "monitoring", target: "launch", type: "supports", weight: 0.3 },
  ],
  "auth",    // start
  "launch",  // end
);

console.log(analysis.pageRank);
// { auth: 0.31, payments: 0.24, launch: 0.22, onboarding: 0.15, monitoring: 0.08 }
// Auth is the most influential node — everything depends on it

console.log(analysis.bottlenecks);
// [{ id: "auth", score: 0.41 }, { id: "payments", score: 0.28 }]

console.log(analysis.criticalPath);
// ["auth", "payments", "launch"] — the shortest path to your goal

console.log(analysis.communities);
// { auth: 0, payments: 0, launch: 0, onboarding: 1, monitoring: 1 }
// Two clusters: core launch path vs. supporting features

For AI Agents

{
  "mcpServers": {
    "oraclaw-graph": {
      "command": "npx",
      "args": ["tsx", "path/to/oraclaw-mcp/index.ts"],
      "description": "Graph analysis — PageRank, communities, critical path, bottleneck detection"
    }
  }
}

MCP Tool: analyze_decision_graph

Agent use cases:

  • "Which of these 20 Jira tickets is blocking the most other work?"
  • "Cluster these 50 features into logical groups for sprint planning"
  • "What's the critical path from current state to product launch?"
  • "Rank these team members by influence in the communication network"

Pricing

| Plan | Price | Analyses/mo | |------|-------|------------| | Free | $0 | 500 | | Starter | $99/mo | 10,000 | | Growth | $499/mo | 100,000 |


@oraclaw/graph is a thin API client. All computation runs server-side. No algorithm source code is included in this package.