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

dotenv-encode

v1.0.5

Published

Downloads

121

Readme

DOTENV-ENCODE

Installation

$ npm install dotenv-encode

Description

Dotenv-encode is a package for encrypting or decrypting a file or folder using a password.

  • Secured: It uses the aes256 algorythm from the crypto package for encrypting a file or folder with a key.
  • Fast and flexible: The command line only take few arguments and can be adapted easily.

Example

Encryption

$ npm dotenv-encode ./env/test.env -o ./encrypted/test.env -s MySecretKey
## Without secret/s, a prompt will ask for the secret
$ npm dotenv-encode ./env/test.env -o ./encrypted/test.env

This command will encrypt the content of the file ./env/test.env in the file ./encrypted/test.env with MySecretKey as password.

You can also encrypt all the file in a folder :

$ npm dotenv-encode ./env -o ./env_encrypted -s MySecretKey

Decryption

$ npm dotenv-encode ./env/test.env -o ./encrypted/test.env -s MySecretKey -d

This command will decrypt the content of the file ./env/test.env in the file ./encrypted/test.env with MySecretKey as password.

Usage

$ dotenv-encode <path-input-file> --options <VALUE>

| Options | Short | Mandatory | Description | | ------------------------ | ----- | --------- | ------------------------------------------------------------------------------------ | | --out | -o | yes | The path of the result file or folder (it will be created if does not exist) | | --secret | -s | no | Specify the password which would be used to encrypt or decrypt the file. | | --decrypt | -d | no | If present, the command will decrypt the input file |

In case the secret is specified, a prompt will ask for the secret. The decrypt option does not take any parameters. The path-input-file is the file on which we will get the data from.

Contributing

The main purpose of this repository is to continue evolving dotenv-encode, making it faster and easier to use. Development of this package happens in the open on GitHub, and I am grateful to anyone contributing bugfixes and improvements. Read below to learn how you can take part in improving Dotenv-encode.

Sending a PR

I am monitoring for pull requests. I will review any pull request and either merge it, request changes to it, or close it with an explanation.

Before submitting a pull request, please make sure the following is done:

  • Actual tests are not break
  • Documentation is still compiling
  • Code coverage is still higher than 85%
  • Your modification has been tested properly
  • Your modification has been documented

License

Dotenv-encode is MIT licensed.