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

vybtest

v0.1.1

Published

AI-Native Testing Framework - Write tests in YAML, get structured output for autonomous TDD

Readme


Installation

npm install -g vybtest

Quick Start

Create player.ts.vyb:

"player starts with full health":
  confidence: 0.95
  when:
    - "player = createPlayer(100, 100)"
  then:
    - "expect: player.health == 100"

Run:

vyb run tests/

Output:

tests:
  - name: player starts with full health
    status: fail
    actual: 50
    expected: 100
    hints:
      - The equality check failed

Your AI reads the structured output, sees actual: 50 vs expected: 100, and fixes the code.

Why Vyb

Traditional test output is designed for humans. Stack traces, diff formatting, ANSI colors. Your AI has to guess what went wrong.

Vyb outputs structured YAML with:

  • Actual and expected values
  • Failure location
  • Pattern-matched hints
  • Confidence guidance

Zero API calls. Zero cost. Just tests that tell AI exactly what failed.

Documentation

Full documentation at vybtest.com

License

MIT