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

stytch-management

v1.1.0

Published

Official Stytch Management API library for Node.js

Readme

Stytch Management Node.js Library

The Stytch Management Node.js library makes it easy to use Stytch's Programmatic Workspace Actions API in Node.js applications.

This library requires Node.js 20 or later.

[!WARNING] This SDK is currently in alpha with potential breaking changes. Use with caution in production environments.

Install

npm install stytch-management

Pre-requisites

You need your Stytch Management API credentials from the workspace management section of your Stytch Dashboard.

Note: These credentials allow you to perform read and write actions on your workspace, potentially modifying or deleting important Stytch resources like projects, environments, or secrets.

Usage

This library supports project- and environment-level actions on the following resources:

  • [x] Projects
  • [x] Environments
  • [x] Country Code Allowlists
  • [x] Email Templates
    • [x] Default Email Templates
  • [x] Environment Metrics
  • [x] Event Log Streaming
  • [x] JWT Templates
  • [x] Password Strength Configuration
  • [x] Public Tokens
  • [x] RBAC Policies (B2B & Consumer)
  • [x] Redirect URLs
  • [x] SDK Configuration (B2B & Consumer)
  • [x] Secrets
  • [x] Trusted Token Profiles
    • [x] PEM Files

Examples

Create a new API client:

import { ManagementClient, ClientConfig } from "stytch-management";

// Set your Stytch Management API credentials.
const config: ClientConfig = {
  workspace_key_id: process.env.STYTCH_WORKSPACE_KEY_ID!,
  workspace_key_secret: process.env.STYTCH_WORKSPACE_KEY_SECRET!,
};

const client = new ManagementClient(config);

Create a new B2B project:

import { projects } from "stytch-management";

const response = await client.projects.create({
  name: "My new project",
  vertical: "B2B" as projects.Vertical,
});

const newProject = response.project;
console.log(`Created project: ${newProject.projectSlug}`);

Get the live environment in the new project:

import { environments } from "stytch-management";

const response = await client.environments.getAll({
  projectSlug: newProject.projectSlug,
});

const liveEnv = response.environments.find(
  (env) => env.type === ("LIVE" as environments.EnvironmentType)
);
console.log(`Live environment: ${liveEnv?.environmentSlug}`);

Alternatively, create a new custom environment:

const response = await client.environments.create({
  projectSlug: newProject.projectSlug,
  name: "My custom environment",
  type: "TEST" as environments.EnvironmentType,
});

const customEnv = response.environment;
console.log(`Created environment: ${customEnv.environmentSlug}`);

Create a new secret in the live environment:

const response = await client.secrets.create({
  projectSlug: newProject.projectSlug,
  environmentSlug: liveEnv.environmentSlug,
});

const secret = response.secret;
console.log(`Created secret: ${secret.secretID}`);

Get SDK configuration:

const response = await client.sdk.getConsumerConfig({
  projectSlug: newProject.projectSlug,
  environmentSlug: liveEnv.environmentSlug,
});

console.log("Consumer SDK config:", response.config);

Type Safety

All request and response types are fully typed. Import them from the specific resource namespaces:

import { projects, environments, secrets } from "stytch-management";

// Use typed requests
const createRequest: projects.CreateRequest = {
  name: "My project",
  vertical: "B2B",
};

// Responses are also typed
const response: projects.CreateResponse = await client.projects.create(
  createRequest
);

Error Handling

import { ManagementStytchError } from "stytch-management";

try {
  await client.projects.get({ projectSlug: "invalid-slug" });
} catch (error) {
  if (error instanceof ManagementStytchError) {
    console.error(`Stytch error: ${error.error_type}`);
    console.error(`Message: ${error.error_message}`);
    console.error(`Request ID: ${error.request_id}`);
  }
  throw error;
}

Running Tests

This library includes comprehensive integration tests that verify functionality against the Stytch API. These tests create and clean up disposable projects and resources.

Prerequisites

To run the tests, you need valid Stytch Management API credentials:

export STYTCH_WORKSPACE_KEY_ID="your-workspace-key-id"
export STYTCH_WORKSPACE_KEY_SECRET="your-workspace-key-secret"

Important: Tests will be skipped if these environment variables are not set. The tests create real resources in your workspace but clean them up automatically.

Running All Tests

# Install dependencies
npm install

# Run all tests
npm test

# Run tests with verbose output
npm test -- --verbose

Running Specific Test Files

# Run a specific test file
npm test -- lib/projects.test.ts

# Run tests matching a pattern
npm test -- --testNamePattern="Secrets"

Test Coverage

The test suite includes integration tests for:

  • Email Templates - Create, get, update, delete, and default management
  • Environments - Environment lifecycle with user locking and IDP configurations
  • Secrets - Secret creation, retrieval, and deletion
  • Public Tokens - Public token management
  • JWT Templates - Session and M2M JWT template configuration
  • Redirect URLs - URL validation and type management
  • Password Strength Config - LUDS and ZXCVBN policy configuration
  • Country Code Allowlist - SMS and WhatsApp country code management

Each test suite:

  • ✓ Creates disposable projects/environments
  • ✓ Tests all CRUD operations
  • ✓ Validates error handling
  • ✓ Cleans up all resources automatically
  • ✓ Runs independently without side effects

Test Output

Tests use Jest and provide detailed output:

PASS lib/secrets.test.ts
  Secrets Integration Tests
    Create
      ✓ should create secret (234ms)
    Get
      ✓ should get existing secret (156ms)
      ✓ should fail when secret does not exist (89ms)
    GetAll
      ✓ should get all secrets (445ms)
    Delete
      ✓ should delete existing secret (178ms)

Continuous Integration

Tests are designed to run in CI environments. Set the environment variables in your CI configuration:

# Example GitHub Actions
env:
  STYTCH_WORKSPACE_KEY_ID: ${{ secrets.STYTCH_WORKSPACE_KEY_ID }}
  STYTCH_WORKSPACE_KEY_SECRET: ${{ secrets.STYTCH_WORKSPACE_KEY_SECRET }}

Development

See DEVELOPMENT.md for information on building and testing the SDK.

Documentation

See the Stytch API Reference for complete documentation on the Management API endpoints.

Support

If you've found a bug, open an issue!

If you have questions or want help troubleshooting, join us in Slack or email [email protected].

If you've found a security vulnerability, please follow our responsible disclosure instructions.

Code of Conduct

Everyone interacting in the Stytch project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.

License

MIT