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

ssh-seed

v1.6.4

Published

A command line tool to generate ssh authenticaiton keys and add them to the ssh agent automatically.

Downloads

17

Readme

ssh-seed

Build Status npm version

A command line tool to generate ssh authenticaiton keys and add them to the ssh agent automatically.

Description

It is boring and tiring to generate many ssh passphrases and authenticaiton keys and add them to the ssh agent. This tool executes that task automatically.

Demo (Gif Animation)

https://giphy.com/gifs/demo-ssh-seed-xUPGcnBZ18P2IchhoQ

This gif animation shows

  1. Install
  2. Create a configuration file skelton
  3. Create multiple passphrases and authenticaiton keys and add keys to the ssh agent by one command (not interactive)

Requirements

  • ssh-add
  • ssh-keygen
  • expect
  • node

Install

$ npm i -g ssh-seed

Usage

To see All available options and subcommand, please see here.

  1. Create the configuration file.
$ ssh-seed init
  1. After edit the configuration file, run ssh-seed
$ ssh-seed

Running ssh-seed with no command will run the 'run' subcommand. The 'run' subcommand creates passphrases and authentication keys and adds keys to ssh-agent.

If you want only to create passphrases and authentication keys but not to add keys to ssh-agent, use the 'keygen' command.

$ ssh-seed keygen

The 'keygen' command was added in v1.1.0 .

If you want only to add existing keys to ssh-agent but not to create new passphrases and authentication keys, use the 'add' command.

$ ssh-seed add

The 'add' command was added in v1.2.0 .

Configuration options

Please see comments of the configuration file.

Configuration file search

When the ssh-seed command is run, the configuration file ssh-seed.yml is searched from the current directory to the root directory in order. If it is found once, the search is stopped. If it is not found, an error is occured.

ssh-seed.pass.yml

When the ssh-seed command generate the authenticaiton keys, at the same time passphrases of them are generated and written in the ssh-seed.pass.yml. The ssh-seed.pass.yml is generated in the directory where ssh-seed.yml is.

Change Log

Please see here. This change log is generated automatically with standard-version.

Contributing

  1. Fork (https://github.com/suzuki-shunsuke/ssh-seed/fork)
  2. Create a feature branch
  3. Commit your changes
  4. Rebase your local changes against the master branch
  5. Run test suite with the npm test command and confirm that it passes
  6. Create a new Pull Request

License

MIT

Author

Suzuki Shunsuke