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

@connected-home/serverless-plugin-kms

v1.0.2

Published

Serverless plugin that decrypts environment variables before deployment

Downloads

8

Readme

serverless-plugin-kms

This serverless plugin is used when you need to store your sensitive environment variables in your codebase.

Why this approach

We prefer saving all config into repos so that we never have to handle git-ignored .env files that live on someone's machine. Checking sensitive data (such as API keys and OAuth tokens) into github is obviously not safe; that's why we encrypt everything first. Then we just add it to config a check it into upstream repo so that the data is never lost.

Big shout-out to beavis07 for this solution.

How to use it

First, encrypt a variable with your us-east-1 KMS key. Then add the value to your serverless environment; the plugin does the rest.

You can define both encrypted and normal values, just make sure an encrypted value is an object with encrypted: true:

{
  "ENCRYPTED_TOKEN": {
    "encrypted": "true",
    "value": "encrypted-value"
  },
  "NORMAL_VARIABLE": "old-fashioned-value"
}

The plugin will translate this before deployment to:

{
  ENCRYPTED_TOKEN: "decrypted-value",
  NORMAL_VARIABLE: "old-fashioned-value"
}

Roadmap

  • try it out with yaml defined environment variables
  • allow specifying KMS key and its region
  • add CLI tool to encrypt and decrypt keys on the fly
  • KMS key rotation