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

@staltz/secret-stack

v6.2.1-1

Published

create secure peer to peer networks using secret-handshakes

Downloads

1

Readme

secret-stack

create secure peer to peer networks using secret-handshakes.

SecretStack is built on secret-handshake and muxrpc. This provides a framework to make building secure, decentralized systems easier. (such as scuttlebot which this was refactored out of ;)

Example

var SecretStack = require('secret-stack')
var databasePlugin = require('./some-database')
var bluetoothPlugin = require('./bluetooth')
var config = require('./some-config')

var App = SecretStack({ appKey: '1KHLiKZvAvjbY1ziZEHMXawbCEIM6qwjCDm3VYRan/s=' })
  .use(databasePlugin)
  .use(bluetoothPlugin)

vap app = App(config)

For documentation on plugins, see PLUGINS.md

API

SecretStack(opts) => App

Initialize a new app factory.

opts is an Object with properties:

  • appKey - String, 32 bytes a high entropy (i.e. random) key which is fixed for your app. Actors who do not know this value will not be able to connect to instances of your app.
  • permissions - Object (optional), you can set default permissions which will be the foundation for all permissions subsequently added

NOTE - you can also add other properties to opts. These will be merged with config later to form the final config passed to each plugin. (i.e. merge(opts, config))

App.use(plugin) => App

Add a plugin to the factory. See PLUGINS.md for more details.

Returns the App (with plugin now installed)

App(config) => app

Start the app and returns an EventEmitter with methods (core and plugin) attached.

config is an (optional) Object with any properties:

  • keys - String a sodium ed25519 key pair
  • ... - (optional)

config will be passed to each plugin as they're initialised (as merge(opts, config) which opts were those options SecretStack factory was initialised with).

app.getAddress()

get a string representing the address of this node. it will be ip:port:<base64:pubkey>.

app.connect(address, cb)

create a rpc connection to another instance. Address should be the form returned by getAddress

app.auth(publicKey, cb)

Query what permissions a given public key is assigned. it's not intended for this to be exposed over the network, but rather to extend this method to create plugable permissions systems.

app.auth.hook(function (auth, args) {
  var pub = args[0]
  var cb = args[1]
  //call the first auth fn, and then hook the callback.
  auth(pub, function (err, perms) {
    if(err)  cb(err)
    //optionally set your own perms for this pubkey.
    else if(accepted)
       cb(null, permissions)

    //or if you wish to reject them
    else if(rejected)
      cb(new Error('reject'))

    //fallback to default (the next hook, or the anonymous config, if defined)
    else
      cb()
  })
})

app.close()

close the app!

Optionally takes (err, callback)


TODO document

mix: I think some of these are exposed over muxrpc (as they're in the manifest) and some can only be run locally if you have access to the instance of app you got returned after initialising it.

app.id => String (alias publicKey)

app.getManifest() => Object (alias: manifest)

auth: 'async'

address: 'sync'

config => Object'

multiserver.parse: 'sync',

multiserver.address: 'sync'

multiserver.transport: 'sync'

multiserver.transform: 'sync'

License

MIT