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

@fillgate/core

v0.3.1

Published

Venue adapters with fee codes baked in, guardrails, fee ledger, geoblock. Zero runtime deps; venue SDKs are optional peers loaded lazily.

Readme

@fillgate/core

Venue adapters with fee codes baked in, plus the guardrails, fee ledger and geoblock that sit in front of them. Zero runtime dependencies; venue SDKs (@solana/web3.js, @polymarket/clob-client-v2, @nktkas/hyperliquid, viem) are optional peers, loaded lazily only for the venues you enable.

Most people want @fillgate/mcp — the MCP server that exposes these adapters as tools to Claude and other agents. Use @fillgate/core directly only if you are embedding the adapters in your own app.

import { loadConfig, enabledVenues, JsonlLedger } from '@fillgate/core'

const config = loadConfig(process.env)   // reads DRY_RUN, MAX_NOTIONAL_USD, MAX_SLIPPAGE_BPS,
                                         // RATE_LIMIT_PER_MIN, FILLGATE_VENUES, venue credentials
enabledVenues(config)                    // ['jupiter', ...] — only fully configured venues

const ledger = new JsonlLedger(config.ledgerPath)  // daily YYYY-MM-DD.jsonl event files
ledger.readAll()   // prepare / execute_attempt / fill / preview / guard_rejection
ledger.summary()   // fills only — the fee-reconciliation view

Every money-moving path is two-step (prepare → execute) and passes through the guardrails in guards.ts. DRY_RUN=true (the default) never broadcasts.

Docs: github.com/mineloop99/fillgate · MIT