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

@wild-framework/graph

v0.2.9

Published

Machine-readable project graph (introspection) for Wild Framework apps — for visual builders and AI agents.

Readme

@wild-framework/graph

Machine-readable Project Graph for Wild Framework apps.

A single JSON-serializable model of a running application — providers, routes, resources, request schemas, DI bindings, and migrations. It is the source of truth that visual builders (Wild Studio) and AI agents render and manipulate.

Install

pnpm add @wild-framework/graph

Usage

Register GraphProvider last (after all feature providers):

import { GraphProvider } from "@wild-framework/graph";

GraphProvider.appName = "Shop API";
GraphProvider.appVersion = "1.0.0";

app.register(GraphProvider); // after feature providers, before/after OpenApi

Then fetch the graph:

curl http://localhost:3000/graph.json

Or build it programmatically:

import { buildProjectGraph } from "@wild-framework/graph";

const graph = buildProjectGraph(app, router, { name: "Shop API", version: "1.0.0" });

Graph shape

{
  "name": "Shop API",
  "version": "1.0.0",
  "providers": [{ "name": "ProductProvider", "index": 8 }],
  "routes": [{ "method": "get", "path": "/products", "controller": "ProductController", "action": "index", "validator": "CreateProductRequest" }],
  "resources": [{ "name": "Product", "segment": "products", "routes": [] }],
  "schemas": [{ "name": "CreateProductRequest", "fields": { "name": "string", "price": "number" } }],
  "bindings": [{ "token": "ProductService" }],
  "migrations": [{ "name": "20261010_add_order_index", "applied": true }]
}

Design

  • Derived from the live app (never hand-maintained) via Application.getRegisteredProviders(), Router.getRegisteredRoutes(), and Container.listBindings().
  • Resources are grouped by first path segment (/products/:id → products).
  • The graph is read-only introspection — the visual builder renders it and maps user actions back to CLI/engine operations (the GUI holds no logic).

License

MIT