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

@openpx/sdk

v0.3.1

Published

Node.js SDK for OpenPX prediction markets

Downloads

752

Readme

@openpx/sdk

npm License: MIT

Node.js SDK for OpenPX — a unified interface for prediction markets.

Installation

npm install @openpx/sdk

Quick Start

const { Exchange } = require("@openpx/sdk");

const exchange = new Exchange("kalshi");
const markets = await exchange.fetchMarkets();

for (const market of markets.slice(0, 5)) {
  console.log(`${market.question}: ${JSON.stringify(market.prices)}`);
}

Supported Exchanges

  • Kalshi — US-regulated event contracts
  • Polymarket — Crypto-native prediction markets

Authentication

Kalshi

const exchange = new Exchange("kalshi", {
  api_key_id: process.env.KALSHI_API_KEY_ID,
  private_key_path: "./kalshi-private-key.pem", // or private_key_pem: "<inline PEM>"
});

Public market-data calls work without credentials.

Polymarket

Pick the credential path that matches your wallet:

| Wallet model | Required keys | | -------------------------------------- | ----------------------------------------------------------- | | MetaMask EOA + Polymarket Safe | private_key (EOA) + funder (Safe) | | Plain EOA (no Safe) | private_key only | | Pre-derived API keys (most reliable) | api_key + api_secret + api_passphrase (+ private_key for order signing) |

const exchange = new Exchange("polymarket", {
  private_key: process.env.POLYMARKET_PRIVATE_KEY,
  funder:      process.env.POLYMARKET_FUNDER, // omit for plain EOA
});

signature_type is auto-detected from funder and almost never needs to be set explicitly. If you set it to "eoa" while a funder is configured, the SDK overrides it to "gnosis_safe" with a warning — that combo is rejected by Polymarket and is a common MetaMask misconfiguration.

If derive-api-key returns a Cloudflare WAF block (datacenter IPs are often blocked), generate keys once via the Polymarket web app and pass them as api_key / api_secret / api_passphrase to skip the derive flow entirely.

Full credential matrix: docs.openpx.io/setup/polymarket-credentials.