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

@chainlink/env-enc

v1.0.5

Published

A tool for loading and storing encrypted environment variables

Downloads

438

Readme

env-enc

A tool for loading and storing encrypted environment variables

What

This is a tool for keeping environment variables such as private keys and other credentials encrypted at rest. This reduces the risk of credential exposure by ensuring credentials are not visible in plaintext or in terminal history. It also allows an encrypted environment variables to be stored on Github, provided they are protected with a secure password.

For loading environment variables, this works in a similar manner to the NPM package dotenv where environment variables are loaded from a .env file. However, this plugin instead uses CLI commands to create an .env.enc file which stores environment variables that are encrypted using a password. Then, when the config() method is called, these variables will be decrypted and loaded into the environment.

Installation

  1. Install @chainlink/env-enc from NPM
  2. Import the package in your project's main file (this will be hardhat.config.js or hardhat.config.ts for HardHat projects)
  • For JavaScript projects, add the following line to the top of main file (usually index.js):

    require("@chainlink/env-enc").config();
  • For Typescript projects, add the following lines to the top of main file (usually index.ts):

    import * as envEnc from "@chainlink/env-enc";
    envEnc.config();

Commands

The following commands accept an optional --path flag followed by a path to the desired encrypted environment variable file. If one does not exist, it will be created automatically by the npx env-enc set command.

The --path flag has no effect on the npx env-enc set-pw command as the password is stored as an ephemeral environment variable for the current terminal session.

| Command | Description | Parameters | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | | npx env-enc set-pw | Sets the password to encrypt and decrypt the environment variable file NOTE: On Windows, this command may show a security confirmation prompt | | | npx env-enc set | Sets and saves variables to the encrypted environment variable file | | | npx env-enc view | Shows all currently saved variables in the encrypted environment variable file | | | npx env-enc remove <name> | Removes a variable from the encrypted environment variable file | name: Variable name | | npx env-enc remove-all | Deletes the encrypted environment variable file | |

Configuration

By default, all encrypted environment variables will be stored in a file named .env.enc in the root directory of your project. However, this file path can be configured using the path option in the config() method as shown below:

require("@chainlink/env-enc").config({ path: './your_directory/my_env.enc' });

Usage

First, set the encryption password by running the command npx env-enc set-password. The password must be set at the beginning of each new session. If this password is lost, there will be no way to recover the encrypted environment variables.

When running this command on a Windows machine, you may receive a security confirmation prompt. Enter "r" to proceed.

NOTE: When you finish each work session, exit your terminal to prevent your password from becoming exposes if your machine is compromised.

Run the command npx env-enc set to set and save environment variables. These variables will be loaded into your environment when the config() method is called. Use npx env-enc view to view all currently saved environment variables. When pressing ENTER, the terminal will be cleared to prevent these values from remaining visible. Running npx env-enc remove VAR_NAME_HERE deletes the specified environment variable. The command npx env-enc remove-all deletes the entire saved environment variable file.

If you lose your password, delete your encrypted environment variable file. If you attempt to load an encrypted environment variable file without the correct password, it will cause an error.