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

@reserve-protocol/sdk

v0.1.2

Published

Core TypeScript SDK for DTF interface integrations.

Readme

@reserve-protocol/sdk

Core TypeScript SDK for DTF integrations.

This package is environment-agnostic. It should work in modern Node, browser apps, React wrappers, scripts, and bots.

Implemented SDK product surface:

  • Index DTFs: Ethereum mainnet, Base, BSC.
  • Account portfolio API reads: current portfolio, historical portfolio, and transactions.

Yield DTF catalog entries and subgraph defaults exist for Ethereum mainnet and Base, but sdk.yield.get and sdk.yield.list are not implemented yet.

Usage

import { createDtfSdk } from "@reserve-protocol/sdk";

const sdk = createDtfSdk();

const dtf = await sdk.index.get({
  address: "0x...",
  chainId: 8453,
});

const indexDtf = sdk.index.ref({
  address: "0x...",
  chainId: 8453,
});

const proposals = await indexDtf.getProposals();
const price = await indexDtf.getPrice();
const brand = await indexDtf.getBrand();
const basketAtBlock = await indexDtf.getBasket(123n);

With explicit configuration:

import { createDtfSdk } from "@reserve-protocol/sdk";

const sdk = createDtfSdk({
  apiBaseUrl: "https://api.reserve.org",
  chains: {
    1: {
      rpcUrls: ["https://eth-mainnet.example"],
    },
  },
});

const dtfs = await sdk.index.list({ chainId: 1 });

GraphQL Codegen

The SDK imports typed GraphQL documents from generated source files. After changing .graphql files or codegen.yml, regenerate them before running the SDK, build, or typecheck:

pnpm graphql:codegen

Generated GraphQL files are checked in so consumers do not need to run codegen after installing the package.

Playground

Run a live Index DTF fetch and print real data:

pnpm playground:index

You can also pass address chainId:

pnpm playground:index 0x4da9a0f397db1397902070f93a4d6ddbc0e0e6e8 8453

This is intentionally not part of the normal test suite or CI path.

Errors

SDK errors use stable machine-readable codes:

import { createDtfSdk, isSdkError } from "@reserve-protocol/sdk";

const sdk = createDtfSdk();
const address = "0x...";
const chainId = 8453;

try {
  await sdk.index.get({ address, chainId });
} catch (error) {
  if (isSdkError(error) && error.code === "RECORD_NOT_FOUND") {
    // handle known SDK error
  }
}

Design

The SDK uses a small domain facade over a runtime client. One-off methods take plain inputs like { address, chainId }. Repeated DTF workflows can use sdk.index.ref({ address, chainId }), which only binds identity and does not fetch by itself.

Do not add a class-based SDK surface unless there is a strong reason.

The intended model:

namespace methods -> client -> small transports -> mappers

See ../../docs/sdk/architecture.md.