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

s3cf1g

v0.0.1

Published

Mini web app to HTTP get encrypted config file.

Downloads

3

Readme

s3cf1g

s3cf1g does one simple job. It checks for the existence of a file, and if it's there, we do nothing.

If it's not there we spin up a web page that asks you to supply a password and URL. We then HTTP GET the file, decrypt it, and save it to disk.

The use case envisioned here is to throw s3cf1g in front of any app that has secrets in its config file (and has HTTP access) and s3cf1g will pull down and decrypt the config file before your app does its normal startup routine.

npm install s3cf1g

Below is an example of using s3cf1g.

url is optional. If not specified it can be supplied on the web form.

const s3cf1g = require('s3cf1g');

const opts = {
  file: '~/some/file.js',
  url: 'https://some/url/file.js'
};

s3cf1g(opts, function(err) {
  if (err) {
    handleErr(err);
  } else {
    // The config file is now safely saved to disk. Now . . .
    doWhateverYouWereGoingToDo();
  }
});

process.env.PORT

The web page we spin up will listen on process.env.PORT || 3000.

export S3CF1G_FORCE=true

If you want to force getting the file (maybe because you know it has been changed on the remote site) just set the S3CF1G_FORCE environment variable to any truthy value.

ez-aes-256-cbc

We use https://github.com/johndstein/ez-aes-256-cbc to decrypt the file, so of course it would have to have been encrypted with ez-aes-256-cbc or other code that uses the same method.