Security News
tea.xyz Spam Plagues npm and RubyGems Package Registries
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
@nullify/libp2p-bundle
Advanced tools
Readme
Basic libp2p bundle with settings that match js-ipfs.
This package provides a zero-config setup to make it easy to include a fully- configured libp2p host in any application. It is almost directly copied from js-ipfs, so you can be confident the settings are compatible. It also allows more nuanced access to the underlying libp2p settings.
npm i @nullify/libp2p-bundle
import create from "@nullify/libp2p-bundle";
const run = async () => {
const node = await create({
multiaddrs: ["/ip4/0.0.0.0/tcp/4007", "/ip4/0.0.0.0/tcp/4008/ws"],
});
const p = new Promise((resolve) => {
// Promise resolves on first discovered peer
node.on("peer:discovery", (peerId) => {
resolve(peerId);
});
});
await node.start();
const listenAddrs = node.transportManager.getAddrs();
console.log("listening on: ", listenAddrs);
const peerId = await p;
console.log(`Discovered: ${peerId.toB58String()}`);
await node.stop();
process.exit();
};
run();
create(options): Promise<import('libp2p')>
/**
* @typedef {Object} Repo
* @property {import('interface-datastore').Datastore} [datastore]
* @property {import('interface-datastore').Datastore} [keys]
*/
/**
* @typedef {Object} Options
* @property {any} [config]
* @property {import('peer-id')} [peerId]
* @property {string[]} [multiaddrs]
* @property {Repo} [repo]
* @property {{ pass?: string }} [keychainConfig]
* @property {import('libp2p').Libp2pConfig} options
*/
/**
* @param {Options} options
* @returns {Promise<import('libp2p')>}
*/
const create = async ({
config,
peerId,
multiaddrs,
repo,
keychainConfig,
options,
}) => {
...
}
The config has defaults for all named options. Usually, you'll only need to follow the usage pattern outlined above. Another common usage pattern is to specify a peerId directly.
import PeerId from "peer-id";
import create from "@nullify/libp2p-bundle";
PeerId.create().then((peerId) => {
create({
peerId,
}).then((node) => {
node.start().then(() => console.log("node started"));
});
});
Unlike a default IPFS peer, libp2p-bundle
defaults to using an in-memory
"repo" for the datastore and keystore. If you want to specify a custom setup
(or mimic the IPFS settings), you an simply provide your own datastore-
compliant storage config:
import LevelStore from "datastore-level";
import { mkdirSync, existsSync } from "fs";
import { join } from "path";
import create from "@nullify/libp2p-bundle";
// Create a persistent on-disk repo for Nodejs demo
const createRepo = (base) => {
if (!existsSync(base)) {
mkdirSync(base);
}
return {
datastore: new LevelStore(join(base, "datastore")),
keys: new LevelStore(join(base, "keys")),
};
};
create({
repo: createRepo("./libp2p"),
}).then((node) => {
node.start().then(() => console.log("node started"));
});
...
PRs accepted.
Small note: If editing the README, please conform to the standard-readme specification.
MIT © 2021 Carson Farmer
FAQs
Basic libp2p bundle with settings that match js-ipfs
The npm package @nullify/libp2p-bundle receives a total of 4 weekly downloads. As such, @nullify/libp2p-bundle popularity was classified as not popular.
We found that @nullify/libp2p-bundle demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
Security News
As cyber threats become more autonomous, AI-powered defenses are crucial for businesses to stay ahead of attackers who can exploit software vulnerabilities at scale.
Security News
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.