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

@rocketbro/weft

v0.1.3

Published

Weft CLI and LSP for machine-checkable specification files

Readme

@rocketbro/weft

Weft CLI and language server for machine-checkable .weft specification files.

Weft exists to solve spec drift: detailed markdown specs become inconsistent as systems evolve, and those mistakes are hard to catch early. @rocketbro/weft gives you a structured spec language plus real-time validation so references, rules, and architecture constraints stay coherent before implementation.

Install

npm install -g @rocketbro/weft

This installs:

  • weft (CLI)
  • weft-lsp (Language Server Protocol server)

CLI Quick Start

weft --help
weft check .
weft stats .
weft deps .
weft contract . --format json

Core Commands

  • weft check [path] validate .weft files
  • weft stats [path] architecture/spec counts
  • weft coverage [path] coverage gaps
  • weft query [path] <query> [args] query rules/types/etc.
  • weft deps [path] dependency graph
  • weft contract [path] [--format text|json] implementation contract
  • weft bootstrap [path] [--target <name>] [--format text|json]
  • weft docs query <terms...> local docs search
  • weft agents print Weft's built-in AGENTS.md guide

Editor Integration

  • VS Code extension wrapper in packages/vscode
  • Zed extension in packages/zed
  • Both use weft-lsp underneath

Example

See:

  • examples/workflow-annotations.weft
  • examples/wild-collab/*.weft

Source

  • Repository: https://github.com/rocketbro/weft