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

@weaveintel/devtools

v0.1.1

Published

Developer tools — scaffold, inspector, validator, mock runtime, migration

Readme

@weaveintel/devtools

Developer conveniences for weaveIntel: scaffold new pieces, inspect what's registered, validate configs, mock a runtime, and plan migrations.

Why it exists

When you're building on a framework, half the friction is the boring setup: writing the same starter file again, squinting at which tools are actually registered, or catching a typo'd config before it fails at runtime. Think of it like the templates and spell-check built into a word processor — you could type every letter and proofread by eye, but the tooling makes the routine parts quick and catches mistakes early. devtools is that convenience layer for weaveIntel: generate a starting point, look inside a running setup, and check your config makes sense.

When to reach for it

Reach for it at build and author time — scaffolding a new agent or tool, printing an inspection report of what's wired up, validating an agent/workflow config, or planning a migration. Grab a createMock* helper when you want a quick inline stub while prototyping. For deterministic test-suite fakes and eval scoring, use @weaveintel/testing instead.

How to use it

import { scaffold, agentConfigValidator, inspect, formatReport } from '@weaveintel/devtools';

// Generate starter files for a new agent
const files = scaffold('agent', { name: 'researcher' });

// Catch config mistakes before runtime
const result = agentConfigValidator.validate({ name: 'researcher', maxSteps: 0 });
if (!result.valid) console.error(result.issues);

// See what's registered
console.log(formatReport(inspect({ /* registries */ })));

What's in the box

  • Scaffoldscaffold, listTemplates (TemplateType, ScaffoldOptions).
  • Inspectorinspect, formatReport (tools, plugins, events → InspectionReport).
  • ValidatorcreateValidator plus ready-made agentConfigValidator, workflowConfigValidator, and rules like requiredFields, maxStepsInRange, validJsonFields.
  • Mock runtimecreateMockModel, createMockEventBus, createMockToolRegistry, createMockRuntime.
  • MigrationplanMigration, formatMigrationPlan.

Single entry point: @weaveintel/devtools.

License

MIT.