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

@ekoindia/eps-sdk

v0.1.0

Published

Backend-only Node.js SDK for Eko Platform Services (EPS) APIs, with request signing built in.

Readme

@ekoindia/eps-sdk

Backend-only Node.js SDK for Eko Platform Services (EPS) APIs, with HMAC request signing baked in.

⚠️ BACKEND-ONLY — never run in a browser

This SDK requires your EPS access_key, which is a server-side secret. The SDK uses it to compute the per-request signature:

secret-key = base64(HMAC-SHA256(timestamp_ms, base64(access_key)))

If the access_key ever reaches a browser, frontend bundle, or any client device, it is compromised. Never instantiate EpsClient in a browser or ship it to the frontend. The constructor throws if it detects a window global as a safety guard, but you are still responsible for keeping the key on the server.

Install

npm install @ekoindia/eps-sdk

Requires Node.js >= 18.

Usage

import { EpsClient } from "@ekoindia/eps-sdk";

const client = new EpsClient({
	developerKey: process.env.EPS_DEVELOPER_KEY,
	accessKey: process.env.EPS_ACCESS_KEY, // server-side secret
	environment: "sandbox", // or "production"
});

// Call an endpoint by its slug; params fill path tokens and the request body.
const result = await client.call("dmt-get-sender", {
	mobile: "9999999999",
});

console.log(result);

new EpsClient(options) accepts:

| Option | Type | Notes | | -------------- | ----------------------------- | ------------------------------------------- | | developerKey | string | Your EPS developer key. | | accessKey | string | Server-side secret used for signing. | | environment | "sandbox" \| "production" | Selects the base URL. | | fetch | typeof fetch (optional) | Inject a custom fetch implementation. | | now | () => number (optional) | Inject a clock (returns timestamp in ms). |

await client.call(slug, params) signs the request, substitutes any {token} path params from params (remaining keys become the JSON body), and returns the parsed JSON response.

A standalone signSecretKey(accessKey, timestamp) helper is also exported if you need to sign requests yourself.

Endpoint catalog

The embedded endpoint catalog (slugs, methods, paths, required params) is generated from the EPS bundle at /agent/sdk-surface.json and shipped as data/sdk-surface.json. It is read at runtime — no network call is needed to resolve a slug.