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

@pooriaarab/vibe-core

v0.2.0

Published

Shared spine for the Vibe Suite: model-preference cascade (agent config → your key → on-device), cross-harness hooks, and the consent ledger that enforces local-first.

Readme

@pooriaarab/vibe-core

npm license

Shared spine for the Vibe Suite — the hard parts every product reuses instead of reimplementing. Three primitives:

npm install @pooriaarab/vibe-core
import { createCascade, createConsentLedger } from '@pooriaarab/vibe-core';

const consent = createConsentLedger();
const cascade = createCascade({ pickLocal, consent });
// declare a capability; get the cheapest, most-private provider that satisfies it
const { provider, tier, egress } = await cascade.resolve({
  capability: 'audio',
  allowEgress: consent.allows('audio'),
});
  1. Model-preference cascade — declare a capability (audio, video, usage-read, …); core resolves the cheapest, most-private provider: agent's existing config → a key you bring → on-device/local. Products never pick a provider directly.
  2. Cross-harness hooks — one normalized VibeEvent stream over Claude Code / Codex / Cursor / Gemini / Grok / pi / Kimi / Hermes / OpenClaw hooks, git hooks, or a watcher floor. Triggers are (timing: sync|async, policy: off|ask|auto).
  3. Consent ledger — the enforcement point for local-first. Any off-machine path (cascade tiers agent/byo, a product's sharing feature) needs a scoped grant; without one, core routes to local or refuses. Makes "no readable data out" real, not aspirational.

Status

v0 — the contract (src/types.ts) is defined. Sub-systems land against it:

| module | fulfils | status | |---|---|---| | cascade/ | Cascade, ResolvedProvider | todo | | adapters/ | HostAdapter per harness, ProviderAdapter per provider | todo | | local/ | LocalRunner (system TTS, Ollama, wasm) | todo | | hooks/ | HookBus + milestone sources | todo | | config/ | layered config + ConsentLedger | todo | | ui/ | terminal kit (spinners, prompts, the local-first badge) | todo |

Design

Full spec: vibelive/docs/vibe-core-spec.md.

Consumers

viberadio · vibemovie · vibedonate · vibelive · vibeshare · vibedating. Published to npm as @pooriaarab/vibe-core; each product depends on it. MIT.