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

@voiceflow/secrets-provider

v1.9.1

Published

Abstraction layer for local/cloud-based secret providers

Downloads

1,927

Readme

circle ci Coverage Quality Gate Status

secrets-provider

Author: Frank Gu <[email protected]>

| Date | Revision | Remarks | | ---- | -------- | ------- | | Sept 10, 2019 | 1.0 | Initial documentation |

Overview

secrets-provider is designed as an NPM package that provides an abstraction for different secret sources. Sources are defined as "providers", and each provider has its own implementation of where and how to fetch and standardize the secrets for presentation.

Design

This module defines a single class, SecretsProvider, that is operated as a singleton. Private object methods (prefixed with underscores) provide the mainfunctionality of secrets processing. Static public accessors and mutators provide the developer-facing API to interact with the secrets manager.

Due to the asynchronous nature of providers and the need for synchronous secrets access, secrets-provider implements a fetch() loop that will execute on a daily basis (0 1 * * *) to grab fresh credentials form the provider. This fetch() function is also called on start(), which loads the initial set of credentials. After start(), users can synchronously get() the latest cached credentials.

At the end of the application lifecycle, the developer should stop() the instance to gracefully clean up the cron job.

Usage

const secretsProvider = require('@voiceflow/secrets-provider');
const config = {
  SECRETS_PROVIDER: 'aws', // 'local', 'test'
  API_KEYS_SECRET: "api_keys_secret_name",    // Only if 'aws'
  MAIN_DB_SECRET: "main_db_secret_name",      // Only if 'aws'
  LOGGING_DB_SECRET: "logging_db_secret_name" // Only if 'aws'
}
// ...

const asyncInitFunction = async () => {
  // ...
  await secretsProvider.start(config);
}

const someFunction = () => {
  const secret = secretsProviders.get('secret_field');
  // Code that uses secret
}

const asyncCleanupFunction = async () => {
  // Cleanup code
  await secretsProvider.stop();
}

Secrets are strictly returned as string type. Checks for database secret fields are implemented for aws provider; it is the responsibility of the developer to ensure that their test and local secrets contain the intended correct information.