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

@elding/sdk

v0.6.20

Published

Protect HTTP API keys with runtime injection and one SDK integration

Readme

@elding/sdk

Protect HTTP API keys without keeping them in your code or .env. In development, Elding's local proxy injects the real key into the outgoing request. In production, the SDK retrieves the key at runtime and your application calls the provider directly.

npm install @elding/sdk

Always install the scoped package @elding/sdk. The unscoped elding package is unrelated.

Quickstart

npx @elding/cli login
npx @elding/cli init
import OpenAI from "openai";
import { configure } from "@elding/sdk";

const openai = new OpenAI(
  await configure("OPENAI_API_KEY", "https://api.openai.com")
);

Start development behind the local proxy:

npx @elding/cli proxy -- npm run dev

configure() — recommended

Use configure(name, target) for HTTP API keys such as OpenAI, Anthropic, Stripe, Resend, Mistral, or any provider authenticated through HTTPS headers.

const { apiKey, baseURL, defaultHeaders } = await configure(
  "PEXELS_API_KEY",
  "https://api.pexels.com"
);

const response = await fetch(`${baseURL}/v1/search?query=nature`, {
  headers: {
    ...defaultHeaders,
    Authorization: apiKey,
  },
});

In development, apiKey is a placeholder and baseURL points to the local proxy. In production, apiKey is retrieved from the vault and baseURL is the provider URL.

Raw API key access

secret(name) and client() are advanced APIs for HTTP API keys that must be loaded into the application process. Prefer configure() whenever the provider supports a custom baseURL and headers.

import { secret, client } from "@elding/sdk";

const apiKey = await secret("OPENAI_API_KEY");

const elding = await client();
const stripeKey = elding.secret("STRIPE_SECRET_KEY");

Elding does not manage non-HTTP application secrets. Keep DATABASE_URL, JWT_SECRET, REDIS_URL, certificates, and database passwords in your platform's environment variables.

Production

Generate a scoped deployment token locally:

npx @elding/cli deploy

Add the emitted variables to your hosting platform:

ELDING_REFRESH_TOKEN=eld_rt_...
ELDING_SET_ID=...

Your application code stays unchanged.

Documentation: https://docs.elding.app/en/sdk/installation