Security News
The Risks of Misguided Research in Supply Chain Security
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
cabal-core
Advanced tools
Core database, replication, and chat APIs for cabal.
npm install cabal-core
var Cabal = require('cabal-node')
Create a cabal p2p database using storage storage
, which must be either a
string (filepath to directory on disk) or an instance of
random-access-storage.
If this is a new database, key
can be omitted and will be generated.
Returns the local user's key (as a string).
Creates a new, live replication stream. This duplex stream can be piped into any transport expressed as a node stream (tcp, websockets, udp, utp, etc).
Retrieve a list of all channel names that exist in this cabal.
Emitted when a new channel is added to the cabal.
Returns a readable stream of messages (most recent first) from a channel.
Pass opts.limit
to set a maximum number of messages to read.
Calls fn
with every new message that arrives, regardless of channel.
Calls fn
with every new message that arrives in channel
.
Emitted when you connect to a peer. key
is a hex string of their public key.
Emitted when you lose a connection to a peer. key
is a hex string of their
public key.
Publish message
to your feed. message
must have a type
field set. If not,
it defaults to chat/text
. In general, a message is formatted as
{
type: 'chat/text',
content: {
text: 'hello world',
channel: 'cabal-dev'
}
}
A timestamp
field is set automatically with the current system time.
type
is an unrestricted field: you can make up new message types and clients
will happily ignore them until someone implements support for them. Well
documented types include
{
type: 'chat/text',
content: {
text: 'whatever the user wants to say',
channel: 'some channel name. if it didnt exist before, it does now!'
}
}
var swarm = require('cabal-core/swarm')
Join the P2P swarm for a cabal, start connecting to peers and replicating messages.
Returns a discovery-swarm.
AGPLv3
[3.0.4] - 2018-11-11
This version was published to npm after 3.1.0
and is almost identical. We therefore only list the changes for 3.0.4
and omit the 3.1.0
version.
topics
(#24) (@nikolaiwarner)cabal.publishChannelTopic()
(#24) (@nikolaiwarner)FAQs
p2p db functions for chat
The npm package cabal-core receives a total of 46 weekly downloads. As such, cabal-core popularity was classified as not popular.
We found that cabal-core demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers 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
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
Research
Security News
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.