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

signed-object

v1.1.1

Published

Signed object creation, and verification complete with salting

Downloads

9

Readme

Signed Object

A config driven tool for signing objects, using the same algorithm implemented by Facebook.

Version npmSupport via GratipayNPM DownloadsBuild StatusDependencies

Install

NPM

$ npm install signed-object --save

Documentation

'new Vault(options)'

options {Object}

Optional. This defaults to your config.signedObject options, and is extended by the passed options. Hence, this can be entirely maintained solely within your config settings.

  • secret {String OR Function}

The secret is used a cryptographic HMAC key. This ensures that your payload cannot be tampered with, as any changes will result in a signature that doesn't match the one produced against your secret.

If a function is passed as the secret, every time sign or verify are invoked, the secret function will be called with the signature (data, cb), where data is the object being signed or verified. For example, this could be used to lookup a secret based off of a key present in your object. When using a function instead of a string, sign and verify both will return promises.

  • ttl {Number}

Optional. If present, any signed object that doesn't already contain an expires property will be appended with a Unix Timestamp relative to the current time, and TTL (Time to Live). This uses milliseconds.

Vault.prototype.sign(data)

Sign the given object, according to options. This will return a string that can be publicly passed around and later verified securely.

Vault.prototype.verify(data)

Sign the given string, according to options. This will return an object if valid, otherwise undefined.

Vault.prototype.inspect(data)

inspects the given signed string, returning it's body as an object regardless of wether it's valid.

Example A

// .
// ├── config
// │   ├── default.json
// │   └── test.json

// test.json
// {
//  ...
//   "signedObject" : {
//     "secret" : "2xYJR\"&QNV6#t4B23*W4Yv5$\"TL),aLsTz9H0(v8d0+zJO8ulw4v495haK*'RD1b",
//     "ttl" : 3600000
//   },
//   ...
// }

var vault = require('signed-object')();

var signed = vault.sign({
  decree: "Install me... and tip",
}); // 'zRWK61EWt66RgLlERkW7sxzJhmb7Rfvax67beDnPXd8.eyJleHBpcmVzIjoxNDM5NDI5Mzg2NzMyLCJkZWNyZWUiOiJJbnN0YWxsIG1lLi4uIGFuZCB0aXAifQ'

var verified = vault.verify(signed);

Example B

var client = require('redis-client-pool').utility;

var vault = require('signed-object')({
  secret: function( data, cb ) {
    client.hget('partner:keys', data.key, cb);
  }
});

...

vault.sign({
  decree: "I'm a little tea pot",
  key: 'https://gratipay.com/Bajix' // fill me up
}).nodeify(cb);

...

vault.verify(signed).nodeify(cb);