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

hyper-ipc-secure

v1.4.48

Published

Hyperswarm IPC Library

Downloads

102

Readme

hyper-ipc-secure

hyper-ipc-secure is a version of hyper-ipc where you can have many named endpoints and the client needs only a pubkey and a name. This library allows you to split your program into different parts, and use it to get one part to ask another to run code, and receive the response, allowing you to expose your functions remotely. The different instances will automatically find each other and connect using a peer-to-peer library called hyperswarm. You can hand the constructor a secret key when you create it to make endpoints harder to guess. Communication is noise encrypted.

Installation

To install hyper-ipc-secure, follow the steps below:

  1. Ensure that you have Node.js and npm installed on your machine.
  2. Run the following command in your terminal:
npm install --save hyper-ipc-secure

This will install hyper-ipc-secure and save it as a dependency in your project.

The different instances will automatically find each other and connect using a peer-to-peer library called hyperswarm.

You can hand the constructor a secret key when you create it to make endpoints harder to guess.

Communication is noise encrypted.

UPDATE:

There is a new webhook client available in this project, this allows you to run a local webhook that executes code on remote hyperswarm based nodes, giving you easy access to all your swarms for webhook based tools like n8n

Usage

Here are some examples of how to use hyper-ipc-secure:

  • Calling remote code with parameters:
const ipc = require('hyper-ipc-secure');
//kp needs at both private and public keys to spawn
const output = await ipc.serve(kp.publicKey, 'hello.world', (input)=>{
    console.log(input);
    return {success:true};
}));
const ipc = require('hyper-ipc-secure');
//kp needs at least publicKey defined to run calls
const output = await ipc.run(kp.publicKey, 'hello.world', {hello:"world"});
console.log(output.success);

Please refer to the examples directory for more detailed examples.

Contributing

We welcome contributions to hyper-ipc-secure! Here are the steps to contribute:

  1. Fork the repository.
  2. Create a new branch for your changes.
  3. Make your changes in your branch.
  4. Submit a pull request with your changes.

Please make sure to update tests as appropriate and follow the code style of the project.