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

@launchpadlab/opensesame

v1.1.1

Published

A simple CLI to manage our app secrets

Downloads

7

Readme

Opensesame CLI

A simple command line interface to store and share non-version controlled application secrets files within the 1Password vault structure.

Setup Instructions

  1. npm install @launchpadlab/opensesame -g
  2. Within your project, ensure a npm command in the package.json file exists for load_secrets: opensesame -d XXX -v XXX -f XXX. If one is not present, add it within the scripts key. For this command -d refers to the document_id in 1Password, -v refers to the vault_id in 1Password, -f refers to the local file_path where the secrets file is located.
{
  ...
  "scripts": {
    ...,
    "load_secrets": "opensesame -d XXX -v XXX -f XXX"
  }
  ...
}
  1. If you know the values for -d -v or -f, please insert those values if not already set. Otherwise the CLI tool will guide you through how to set those.
  2. Run the command npm run load_secrets and follow on-screen instructions

Manual Instructions

If you prefer, you can manually perform the initial steps and use the CLI for syncing secrets files and diff-ing.

  1. Login to 1Password and create a new vault (grab the id of the vault as that will be used for the -v argument to the CLI)
  2. Within that vault, upload the secrets file to create a new document (grab the id of the document as that will be used for the -d argument to the CLI)
  3. Add the secrets file previously uploaded to 1Password in your project folder and make sure it is not tracked in version control. Grab the file_path within your project for the secrets file as that will be used for the -f argument to the CLI
  4. Within the project's package.json file, add a new key within the scripts block for load_secrets: opensesame -d XXX -v XXX -f XXX making sure to replace the XXX values with the respective values captured in the previous steps.
  5. Run the command npm run load_secrets and follow on-screen instructions to sync secrets files within 1Password
  6. If node or a package.json file is not used for a given project, a direct invocation of the CLI can be used with opensesame -d XXX -v XXX -f XXX. Note: This will only work if the flag values are already set for -d, -v, and -f.

FAQs

  • This CLI tool can be used to sync any non-version controlled file into 1Password. Typically this is a .env or application.yml file. However, it can also be used with rails credentials to be used to sync the .key files that are not version controlled.
  • To interact with 1Password directly, you can reference their documentation.

Maintainers Only: Publish Command

  1. npm publish --access restricted