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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@samrahimi/key-mixer

v0.1.1

Published

A Node.js module for managing and distributing API keys from a JSON keystore

Downloads

21

Readme

key-mixer getting started guide

what is key-mixer?

A simple key manager and keystore that supports multiple keys per service, load balancing between keys to allow for consolidation of credit balances and free tier quotas. While there is no advanced security, its more secure than how most ppl use .env, and a heck of a lot more useful

creating your initial keystore

  1. Gather your API keys for various 3rd party services, the keys you probably currently have in .env
  2. Create your keystore.json file, based on keystore.example.json - its really self explanatory.
  3. Remove the environment variables from .env where the keys previously resided, and replace with just one: KEYSTORE_PATH, the complete path to your keystore.json (or whatever else you might have named it)
  4. (TODO) if someone wants to make a utility that sweeps your .env for API keys and does the above steps automagically, do it and submit a PR

using the key mixer, and migrating from process.env

Let's say you have a function like this:

... other code ...
const getChatCompletion = (prompt) => {
  const OpenAI = require("openai")
  const openai = new OpenAI({apiKey: process.env.OPENAI_API_KEY})
  ... call the api, etc ...
}

Assuming you used "OPENAI_API_KEY" as the service name in your keystore, the updated version is as follows:

const keyMixer = require('./keyMixer');
... other code ...
const getChatCompletion = (prompt) => {
  const OpenAI = require("openai")
 //keyMixer.get will round-robin thru the available keys for the requested service as it gets called repeatedly
 const openai = new OpenAI({apiKey: keyMixer.get("OPENAI_API_KEY")})
  ... call the api, etc ...
}

everything else

is an exercise for the reader. Enjoy :)