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

express-minisign

v0.0.1

Published

An express based middleware for using minisign to serve signed files

Downloads

6

Readme

express-minisign

Currently unsupported in Node 12

A Minisign based middlware for express.

Based on Minisign and it's JavaScript API, this middleware allows you to serve up files for clients to download which include a header that can be verified against your Minisign public key.

Usage

Create a public/secret key pair

You'll need to create a Minisign instance on your server and generate a public/secret key pair. The public key should be served on it's own route so that clients can verify future downloads with it, the password and private key should be kept private.

Serve downloads that have been signed

The middleware takes options that include:

minisignPassword: This is a plaintext password that is used when you generate your public and secret key pair. It should be stored somewhere safely on your server.

minisignSecretKeyFilePath: This is the path to the private key file. this file should not be served publicly and should be stored somewhere your server has access to.

serveFile/filePath:

serveFile should be a function that returns an object containing a filePath.

filePath should be an object that has a filePath.

Only one of either serveFile or filePath these should be included in the options object

This will be the file that is signed and offered fow download to the client.

const getFile = (fileName) => {
    //do something with the filename
    return { filePath: pathToFile}
};
const options = {
    minisignPassword: password,
    minisignSecretKeyFilePath: pathToSecretKey,
    serveFile: getFile,
};

app.use('/download', minisignExpress(options));

or

const filePath = {filePath: pathToFile};
const options = {
    minisignPassword: password,
    minisignSecretKeyFilePath: pathToSecretKey,
    filePath: filePath,
};

app.use('/download', minisignExpress(options));

Optional options

The following are optional options.

sendFileOptions, default to {}

The express res.sendFile() options. If not passed through, it will default to an empty object: let obj = {};

options.signContentOptions, default to {}

The minisign javascript options. If not passed through, it will default to an empty object: let obj = {};

Usage for clients

The client will be served the exact same file they expect, however they have the opportunity of being able to verify the file is from you by using Minisign to verify the file.

A header of x-file-minisign-signature is included in the response that contains the signature in base64 format. This can be then decoded using:

const signatureBase64 = Buffer.from(res.header['x-file-minisign-signature'], 'base64');
const signatureAsString = signatureBase64.toString('ascii');

Where the decoded signature can then be passed to the clients implementation of Minisign, along with your public key and the file you served to be verified.