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

getsecret

v1.0.2

Published

a simple api for retrieving secrets stored in yaml files and environment variables

Downloads

12

Readme

getsecret

A simple way to get credentials stored in yaml files and environment variables

Install

npm install getsecret

Storing secrets

You can store secrets in 3 locations (in decreasing order of priority)

  • An environment variable. These are commonly used in Heroku. ex: process.env.some_keyname

  • A file named .getsecret.yaml in your current directory

  • A file named .getsecret.yaml in your home directory. The format should map key names to secrets, ie:

    some_keyname: some_secret_value another_keyname: another_secret_value

Accessing secrets from code

Simply pass the key name to getsecret and its value will be returned. ex:

var getsecret = require('getsecret')
var secret_value = getsecret('some_keyname')

Author

Geza Kovacs

License

MIT