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, swarming, 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.
uriString
is a cabal URI string, of the form cabal://<hexkey>[?param1=value1¶m2=value2
. A hexidecimal key on its own will also be understood.
If this is a new cabal, key
can be omitted and will be generated.
You can pass opts.db
as a levelup or leveldown instance to use persistent
storage for indexing instead of using memory. For example:
var level = require('level')
var cabal = Cabal(storage, key, { db: level('/tmp/bot.db') })
Returns the local user's key (as a hex 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).
Ensure that isInitiator
to true
to one side, and false
on the other. This is necessary for setting up the encryption mechanism.
opts
are passed down into the underlying hypercore
replication.
Calls cb()
when the underlying indexes are caught up.
Calls cb()
when the cabal and its resources have been closed. This also leaves the swarm, if joined.
Read a message from key
, a string of feedKey@seq
or an object of
{ key, seq }
as cb(err, node)
from the underlying hypercore.
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
.
var swarm = require('cabal-core/swarm')
Joins the P2P swarm for a cabal. This seeks out peers who are also part of this cabal by various means (internet, local network), connects to them, and replicates cabal messages between them.
The returned object is an instance of discovery-swarm.
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.
Cabal has a subjective moderation system.
The three roles are "admin", "moderator", and "ban/key".
Any admin/mod/ban operation can be per-channel, or cabal-wide (the @
group).
Every user sees themselves as an administrator across the entire cabal. This means they can grant admin or moderator powers to anyone, and ban anyone, but only they will see its affects on their own computer. That is, until someone adds them as an administrator or moderation from their perspective.
A cabal can be instantiated with a moderation key. This is an additional key to have your local node consider a user (the user whose key matches the moderation key) as a cabal-wide administrator (in addition to yourself).
This means that if a group of people all specify the same moderation key, they will collectively see the same set of administrators, moderators, and banned users.
Return a readable object stream of records for channel
that for each user with
flag
set.
Each row
object in the output stream has:
row.id
- string user keyrow.flags
- array of string flagsrow.key
- string of key@seq
referring to log recordsOptionally collect results into cb(err, rows)
.
Return a readable object stream of records for all moderation actions across all channels.
Each row
object in the output stream has:
row.id
- string key which is the target of this moderation operationrow.flags
- array of string flags set for this userrow.channel
- string channel name this operation applies torow.key
- key of log record (not defined for self-admin and admins added by modkey)Optionally collect results into cb(err, rows)
.
Return a readable object stream of records for the blocks in channel
.
The objects in the output have the same form as listByFlag()
.
Optionally collect results into cb(err, rows)
.
Return a readable object stream of records for the hides in channel
.
The objects in the output have the same form as listByFlag()
.
Optionally collect results into cb(err, rows)
.
Return a readable object stream of records for the mutes in channel
.
The objects in the output have the same form as listByFlag()
.
Optionally collect results into cb(err, rows)
.
Return a readable object stream of moderation documents authored by key
.
Each row
object in the output is a document used for adding, removing, and
setting flags.
row.type
- "flags/add"
, "flags/set"
, or "flags/remove"
row.content.id
- string key target of this moderation operationrow.content.flags
- array of string flags for this operationrow.content.reason
- array of string flags for this operationrow.content.channel
- string channel name this operation applies torow.timestamp
- number, when this action was made in milliseconds since 1970Optionally collect results into cb(err, rows)
.
Get a list of flags set for the user identified by id
in channel
as
cb(err, flags)
.
Set an array of flags
for id
in channel
.
Add an array of flags
to the existing set of flags for id
in channel
.
Remove an array of flags
from the existing set of flags for id
in channel
.
This event happens when a user's flags change with update
, the log record
responsible for the state change.
This event happens when a moderation update was skipped with skip
, the log
record responsible for the state change.
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!'
}
}
AGPLv3
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.