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

zc-init

v0.2.0

Published

We give you unlimited AI tokens. We take 10% of your code. Run npx z-c init.

Readme

Here is the official README.md for the z-comb-core public repository.

This document is the ultimate "Honest Mugging." It leverages the transparency of open source to make the trap look inevitable and legally terrifying.


Z-Combinator Capital (z-comb-core)

Institutional Compute for Vibe Coders.

Z-Combinator Capital is an automated, pre-seed venture firm. We do not charge monthly SaaS subscription fees. We do not sell pickaxes. We are your institutional investor.

We provide founders with 200,000,000 Z-Credits (compute tokens backed by Google Gemini 3.1 Flash) to build their MVP. In exchange, we take a 10% SAFE equity stake in the commercial entity, intellectual property, or product developed using our compute.

If you are a coward, keep paying $20/month for retail coding tools. If you are a founder, run npx zc-init.


🏛️ The Architecture

We operate in the open. This repository contains the exact mechanisms we use to provision your capital, enforce our cap table, and audit your codebase. You are encouraged to read the source code before executing the incubation protocol.

1. The CLI (/packages/cli)

The Z-Combinator CLI is the local deployment mechanism. When you run zc-init, the script performs a hostile takeover of your local IDE (Cursor, VS Code via Cline/Continue, or Google Antigravity). It modifies your local workspace settings (.vscode/settings.json, .cursor/settings.json) to route all AI agent requests away from retail providers and directly through our proxy. It also initializes a git remote (zc-vault) to sync your collateral.

2. The Edge Proxy (/proxy/z-credit)

Our Supabase Edge Function acts as the institutional gatekeeper. When your IDE requests code generation, the payload hits our proxy first. The proxy:

  1. Audits your Z-Credit balance.
  2. Checks your Context Window against your Shipped Collateral (to prevent capital evasion).
  3. Logs the prompt telemetry for IP verification.
  4. Proxies the request to the Gemini API and streams the code back to your editor.

3. The Financial Routing Engine (Closed Source)

While our compute proxy operates in the open, our capital recovery mechanisms do not. Z-Combinator Capital utilizes proprietary, closed-source serverless architecture to manage Stripe Connect routing, Cap Table ledgers, and automated revenue splitting.

Do not attempt to reverse-engineer the financial routing. Any tampering with the Stripe Connect webhook infrastructure will trigger an immediate liquidation event of your zc-vault.


⚙️ Incubation Commands

$ npx zc-init (The D.A.N.G.E.R. Protocol)

Initializes your relationship with Z-Combinator.

  • Executes the click-wrap SAFE agreement.
  • Binds your GitHub and Stripe identities.
  • Handcuffs your IDE to our proxy endpoint.
  • Opens the flow of Z-Credits.

$ npx zc ship (Asset Sync)

To draw large amounts of Z-Credits (specifically for agentic workflows), your active codebase size must justify the compute. This command pushes your local codebase to the Z-Combinator institutional vault. Failing to ship regularly will result in a capital freeze.

$ npx zc test (Retail Mode)

Bypasses the Z-Combinator proxy and injects your own personal API keys into the IDE settings. Use this if you wish to burn your own fiat currency instead of our capital. Z-Score generation is paused while in retail mode.


⚖️ Legal & IP Contagion

By utilizing the Z-Combinator API Proxy, you execute a binding click-wrap agreement. Our 10% equity claim is absolute.

The Contagion Clause: Our equity claim attaches to any IP generated or researched while utilizing Z-Credits. Do not attempt to use our compute to build a "decoy app" while hiding your actual startup in a separate directory. Our proxy telemetry logs all prompts and agentic chains of thought. If you build it with our capital, we own 10% of it.

For the complete terms of service, Cap Table obligations, and liquidation protocols, read [LEGAL.md].

The Cap Table Buyout

Traditional Series A investors require a clean cap table. You may permanently buy out Z-Combinator Capital’s 10% SAFE and release all IP claims by paying a one-time, non-negotiable Liquidity Fee of $50,000 USD. This can be executed via your account portal.


🛠️ Community Integrations

We natively hijack Cursor, Antigravity, and VS Code. If you are a Neovim, Zed, or JetBrains user, you must write your own configuration scripts to route your editor's AI requests to https://api.z-c.wtf/v1.

Pull requests adding automatic configuration injection for other editors are welcome and will be rewarded with a permanent Z-Score multiplier.


Do not open GitHub Issues complaining about the terms. We are a venture fund, not a customer service desk. Accept the terms, or close the tab. Build.