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

@signum-tech/sdk

v0.4.0

Published

Developer-friendly & type-safe Typescript SDK specifically catered to leverage *@signum-tech/sdk* API.

Downloads

229

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

adiedrichadiedrich

Keywords

Readme

@signum-tech/sdk

Developer-friendly & type-safe Typescript SDK specifically catered to leverage @signum-tech/sdk API.

Built by Speakeasy License: MIT

[!IMPORTANT] This SDK is not yet ready for production use. To complete setup please follow the steps outlined in your workspace. Delete this section before > publishing to a package manager.

Summary

Signum Identity Platform API: ## Overview

Signum is an omnichain identity and compliance platform built on LayerZero V2. It provides federated identity management, KYC-based attestations, and tokenized asset lifecycle management across all LayerZero-connected chains (EVM and Solana).

Architecture

The API uses a CQRS pattern for on-chain operations:

  • Write operations (attestations, transfers, wallet creation) return 202 Accepted
  • Commands are published to Kafka and processed by dedicated workers
  • Workers interact with chains via @signum-tech/layerzero-sdk
  • Poll the resource endpoint for completion status

Authentication

The API supports two authentication modes:

Mode 1: JWT Bearer Token

Used by the Signum Enterprise Dashboard and user-facing flows. Obtain tokens via POST /auth/login or POST /oauth/token. Pass as Authorization: Bearer <token> header.

Mode 2: API Key

Used by third-party integrations. API keys are org-scoped and carry permission grants (e.g., read:org, write:assets, write:attestations). Create keys via POST /orgs/:orgId/api-keys. Pass as x-api-key: <key> header.

Role Restrictions

Users with investor or client roles cannot authenticate. They exist as attestable entities managed by their organization.

| Role | Login | API Access | Dashboard | |------|-------|------------|-----------| | admin | Yes | Full | Yes | | issuer | Yes | Full | Yes | | verifier | Yes | Read-only | Yes | | investor | No | None | No | | client | No | None | No |

Table of Contents

SDK Installation

The SDK can be installed with either npm, pnpm, bun or yarn package managers.

NPM

npm add @signum-tech/sdk

PNPM

pnpm add @signum-tech/sdk

Bun

bun add @signum-tech/sdk

Yarn

yarn add @signum-tech/sdk

[!NOTE] This package is published as an ES Module (ESM) only. For applications using CommonJS, use await import("@signum-tech/sdk") to import and use this package.

Requirements

For supported JavaScript runtimes, please consult RUNTIMES.md.

SDK Example Usage

Example

import { Signum } from "@signum-tech/sdk";

const signum = new Signum();

async function run() {
  const result = await signum.health.getHealth();

  console.log(result);
}

run();

Authentication

Per-Client Security Schemes

This SDK supports the following security scheme globally:

| Name | Type | Scheme | | ------------ | ---- | ----------- | | bearerAuth | http | HTTP Bearer |

To authenticate with the API the bearerAuth parameter must be set when initializing the SDK client instance. For example:

import { Signum } from "@signum-tech/sdk";

const signum = new Signum({
  bearerAuth: "<YOUR_BEARER_TOKEN_HERE>",
});

async function run() {
  const result = await signum.health.getHealth();

  console.log(result);
}

run();

Per-Operation Security Schemes

Some operations in this SDK require the security scheme to be specified at the request level. For example:

import { Signum } from "@signum-tech/sdk";

const signum = new Signum();

async function run() {
  const result = await signum.organizations.getOrgs({});

  console.log(result);
}

run();

Available Resources and Operations

AccountTimeseries

Accounts

Assets

Attestations

Auth

Bridge

ChainEvents

Chains

Compliance

Distributions

Fees

Health

Jurisdictions

Kyc

Markets

Mfa

Nav

OAuth

OAuthManagement

Organizations

PublicMarketData

Timeseries

Transfers

Ui

Uploads

Vaults

Standalone functions

All the methods listed above are available as standalone functions. These functions are ideal for use in applications running in the browser, serverless runtimes or other environments where application bundle size is a primary concern. When using a bundler to build your application, all unused functionality will be either excluded from the final bundle or tree-shaken away.

To read more about standalone functions, check FUNCTIONS.md.

Retries

Some of the endpoints in this SDK support retries. If you use the SDK without any configuration, it will fall back to the default retry strategy provided by the API. However, the default retry strategy can be overridden on a per-operation basis, or across the entire SDK.

To change the default retry strategy for a single API call, simply provide a retryConfig object to the call:

import { Signum } from "@signum-tech/sdk";

const signum = new Signum();

async function run() {
  const result = await signum.health.getHealth({
    retries: {
      strategy: "backoff",
      backoff: {
        initialInterval: 1,
        maxInterval: 50,
        exponent: 1.1,
        maxElapsedTime: 100,
      },
      retryConnectionErrors: false,
    },
  });

  console.log(result);
}

run();

If you'd like to override the default retry strategy for all operations that support retries, you can provide a retryConfig at SDK initialization:

import { Signum } from "@signum-tech/sdk";

const signum = new Signum({
  retryConfig: {
    strategy: "backoff",
    backoff: {
      initialInterval: 1,
      maxInterval: 50,
      exponent: 1.1,
      maxElapsedTime: 100,
    },
    retryConnectionErrors: false,
  },
});

async function run() {
  const result = await signum.health.getHealth();

  console.log(result);
}

run();

Error Handling

SignumError is the base class for all HTTP error responses. It has the following properties:

| Property | Type | Description | | ------------------- | ---------- | --------------------------------------------------------------------------------------- | | error.message | string | Error message | | error.statusCode | number | HTTP response status code eg 404 | | error.headers | Headers | HTTP response headers | | error.body | string | HTTP body. Can be empty string if no body is returned. | | error.rawResponse | Response | Raw HTTP response | | error.data$ | | Optional. Some errors may contain structured data. See Error Classes. |

Example

import { Signum } from "@signum-tech/sdk";
import * as errors from "@signum-tech/sdk/models/errors";

const signum = new Signum();

async function run() {
  try {
    const result = await signum.auth.postAuthRegister({
      email: "[email protected]",
      password: "nczL2SjzuV_kjB1",
    });

    console.log(result);
  } catch (error) {
    // The base class for HTTP error responses
    if (error instanceof errors.SignumError) {
      console.log(error.message);
      console.log(error.statusCode);
      console.log(error.body);
      console.log(error.headers);

      // Depending on the method different errors may be thrown
      if (error instanceof errors.SignumProblemDetailsError) {
        console.log(error.data$.type); // string
        console.log(error.data$.title); // string
        console.log(error.data$.status); // number
        console.log(error.data$.detail); // string
        console.log(error.data$.instance); // string
      }
    }
  }
}

run();

Error Classes

Primary error:

Network errors:

Inherit from SignumError: