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

@flo-fi/sdk

v0.1.0

Published

TypeScript client for the Flo partner API. Authenticates with an sk_test_ or sk_live_ key.

Readme

@flo-fi/sdk

TypeScript client for the Flo partner gateway. Pass an sk_test_ or sk_live_ key. The gateway authenticates the key and does not forward the secret.

import { Flo, WebhookVerifier } from "@flo-fi/sdk";

const flo = new Flo({
  apiKey: process.env.FLO_API_KEY!,
  baseUrl: "https://api.dev.gm.markets",
});

const history = await flo.orders.history({ chainId: 421614 });
const accepted = new WebhookVerifier().verify({ secret, timestamp, body, signature });

Flo is the entry point. Each console area is its own class:

| Class | Calls | |---|---| | flo.business | me, organizationId | | flo.contracts | list, approved, submit, address | | flo.orders | list, audit, status, statusBatch, mints, redemptions, history | | flo.catalog | chains, symbols, quotes, snapshots, list, assetRequests, requestAsset | | flo.webhooks | list, create, rotate, delete, test | | flo.activity | balance, sandboxFaucet, events | | flo.signing | sign | | flo.feed | socket reads on /fed/ws: snapshots, candles, sparklines, tape, order flow, corporate actions |

RequestValidator checks addresses, URLs, tickers, order sides, and sign bodies before the request. HistoryMapper builds the buy, sell, deposit, and withdrawal rows. QuoteBook reads token prices. WebhookVerifier checks x-flo-signature.

Verification, team, logos, and API key management stay in the console.

signing.sign uses the key owner's wallet as owner and receiver. The GM partner fee-voucher route stays out of this client.

flo.feed opens a WebSocket to /fed/ws. The gateway checks the API key and passes each read through to the feed service. This client sends at most 100 messages a second; a faster loop fails locally with WS_RATE_LIMITED and does not put that cap on the feed service.

const snapshot = await flo.feed.snapshot("AAPL");
const candles = await flo.feed.candles({ symbol: "AAPL", interval: "1Min" });