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

@angloqq03/ekr

v1.1.1

Published

Pick a random API key (or any env entry) from dotenv-style files and JSON.

Readme

@angloqq03/ekr

Pick a random API key (or any env entry) from dotenv-style files and JSON.

  • Supported formats: .env / .txt / .keys (dotenv lines), plus .json
  • Works in the browser (string input) and in Node (file loading + discovery)

Install

npm i @angloqq03/ekr

Quick usage (Vite/React/Vue/etc.)

import { parseDotenv, pickRandom } from "@angloqq03/ekr";

const entries = parseDotenv(`
KEY1="A"
KEY1="B"
KEY2="C"
`);

const chosen = pickRandom(entries, { key: "KEY1" });
console.log(chosen.key, chosen.value);

File formats

Dotenv-style (.env, .txt, .keys)

Anything that looks like KEY="VALUE" is supported:

API_KEY="abc"
API_KEY="def"
OTHER="123"

Duplicate keys are kept (so pickRandom(..., { key: "API_KEY" }) makes sense).

JSON (.json)

Object form:

{ "API_KEY": "abc", "OTHER": "123" }

Array form:

[{ "key": "API_KEY", "value": "abc" }, { "key": "API_KEY", "value": "def" }]

Node usage (load from files)

import { pickRandomFromFile } from "@angloqq03/ekr/node";

const entry = await pickRandomFromFile("./keys.env", { key: "API_KEY" });
console.log(entry);

Auto-discover key files in a folder

pickRandomDiscovered() searches a directory for supported files and picks from all of them.

import { pickRandomDiscovered } from "@angloqq03/ekr/node";

const entry = await pickRandomDiscovered({ dir: process.cwd(), key: "API_KEY" });
console.log(entry.key, entry.value, entry.sourcePath);

Discovery includes common names like .env, .env.local, .keys, keys.txt, keys.json and will also scan the directory for files ending in .env, .keys, .txt, .json.

CLI

After install:

npx @angloqq03/ekr --file ./.env --key API_KEY

Auto-discover in the current directory:

npx @angloqq03/ekr --dir . --show-source

Output formats:

npx @angloqq03/ekr --file ./keys.json --format json
npx @angloqq03/ekr --file ./keys.env --format value

API

  • parseDotenv(content, { keepDuplicates?: boolean })
  • parseJsonKeys(content)
  • pickRandom(entries, { key?: string, rng?: () => number })
  • toDotenvLine({ key, value })
  • Node-only: pickRandomFromFile(path, { key?, format? }), pickRandomDiscovered({ dir?, key? })

Notes

  • This tool doesn’t modify your .env file. It just reads/parses and returns a value.
  • Treat key files as secrets: don’t commit real API keys to git, and don’t ship them to the browser unless you intend them to be public.