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

vs-cubby

v1.0.2

Published

A tool to help make it easier to interact with the cubby hole pattern and HashiCorp Vault

Downloads

7

Readme

cubby Build Status

Cubby is a command line tool used to help make interacting with Hashicorp's Vault cubbyhold pattern much less painful.

Reference

How it Works

  1. You will need to be authenticated with vault. I.E. you will need to have a token at ~/.vault-token.
  2. The VAULT_ADDR environment variable will need to be set to your instances of vault.

According to the cubbyhole pattern, we should not be passing around authentication tokens. If we must (which we usually do with machines) we should only pass around tokens that have a very short ttl and a usage limit of 2.

Cubby helps facilitate this through Vaults http API. It works in this order:

  • Create the Temporary Token (The Temporary token assumes the default policy)
  • Create the Permanent Token
  • Store the Permanent Token in the cubbyhole/token secret backend with the Temporary token (1 use)
  • Give the Temporary Token to STDOUT.

In the end, you'll get a temporary token that has 1 use left that you can pass to your army of machines.

Installation

npm install -g vs-cubby

Usage

cubby -help

[options]
-t, --ttl:		The time to live for the temporary token. (Default 15m)
-p, --policy:	A policy to associate with the permanent token. Can be used multiple times.

cubby -t 5m -p engineers -p notadmins

Development

We like to use coffeescript and grunt here at VeriShip, so in order to build and run all tests, simply run:

npm run dev

This will compile all source and test files then run all the tests.

Contributing

If you encounter a bug or would like a feature that is not a part of Cubby yet, please fork and submit a pull request!

License

MIT License

Copyright (c) 2016 VeriShip Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.