Security News
PyPI Introduces Digital Attestations to Strengthen Python Package Security
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
Distributed single writer key/value store
npm install hypertrie
Uses a rolling hash array mapped trie to index key/value data on top of a hypercore.
Useful if you just want a straight forward single writer kv store or if you are looking for a building block for building more complex multiwriter databases on top.
const hypertrie = require('hypertrie')
const db = hypertrie('./trie.db', {valueEncoding: 'json'})
db.put('hello', 'world', function () {
db.get('hello', console.log)
})
db = hypertrie(storage, [key], [options])
Create a new database. Options include:
{
feed: aHypercore, // use this feed instead of loading storage
valueEncoding: 'json' // set value encoding
}
If you set options.feed
then you can set storage
to null.
db.get(key, [options], callback)
Lookup a key. Returns a result node if found or null
otherwise.
Options are passed through to hypercore's get method.
db.put(key, value, [options], [callback])
Insert a value.
Options can include:
{
condition: function (oldNode, newNode, cb(err, bool)) { ... }
}
The optional condition
function provides atomic compare-and-swap semantics, allowing you to optionally abort a put based on the current and intended node values.
The condition callback should be used as follows:
cb(new Error(...))
: Abort with an error that will be forwarded through the put
.cb(null, false)
: Abort the put, but do not produce an error.cb(null, true)
: Proceed with the put.db.del(key, [options], [callback])
Delete a key from the database.
Options can include:
{
condition: function (oldNode, cb(err, bool)) { ... }
}
The optional condition
function behaves the same as the one in put
, minus the newNode
parameter.
db.batch(batch, [callback])
Insert/delete multiple values atomically. The batch objects should look like this:
{
type: 'put' | 'del',
key: 'key/we/are/updating',
value: optionalValue
}
const watcher = db.watch(prefix, [onchange])
Watch a prefix of the db and get notified when it changes.
When there is a change watcher.on('change')
is emitted.
Use watcher.destroy()
to stop watching.
db.on('ready')
Emitted when the db has loaded it's internal state.
You do not need to wait for this unless noted in the docs.
db.version
Returns the current version of the db (an incrementing integer).
Only available after ready
has been emitted.
db.key
Returns the db public key. You need to pass this to other instances you want to replicate with.
Only available after ready
has been emitted.
db.discoveryKey
Returns the db discovery key. Can be used to find other db peers.
Only available after ready
has been emitted.
checkoutDb = db.checkout(version)
Returns a new db instance checked out at the version specified.
checkoutDb = db.snapshot()
Same as checkout but just returns the latest version as a checkout.
stream = db.replicate([options])
Returns a hypercore replication stream for the db. Pipe this together with another hypertrie instance.
All options are forwarded to hypercores replicate method.
ite = db.iterator(prefix, [options])
Returns a nanoiterator that iterates the latest values in the prefix specified.
Options include:
{
recursive: true
}
If you set recursive: false
it will only iterate the immediate children (similar to readdir)
Additional options are passed through to hypercore's get method.
stream = db.createReadStream(prefix, [options])
Same as above but as a stream
db.list(prefix, [options], callback)
Creates an iterator for the prefix with the specified options and buffers it into an array that is passed to the callback.
stream = db.createWriteStream()
A writable stream you can write batch objects to, to update the db.
ite = db.history([options])
Returns a nanoiterator that iterates over the feed in causal order.
Options include:
{
gt: seq,
lt: seq,
gte: seq,
lte: seq,
live: false // set to true to keep iterating forever
}
stream = db.createHistoryStream([options])
Same as above but as a stream
ite = db.diff(version, [prefix], [options])
Returns a nanoiterator that iterates the diff between the current db and the version you specifiy. The objects returned look like this
{
key: 'node-key-that-is-updated',
left: <node>,
right: <node>
}
If a node is in the current db but not in the version you are diffing against
left
will be set to the current node and right
will be null and vice versa.
Options include:
{
skipLeftNull: false,
skipRightNull: false
}
stream = db.createDiffStream(version, [prefix])
Same as above but as a stream
MIT
FAQs
Distributed single writer key/value store
The npm package hypertrie receives a total of 10 weekly downloads. As such, hypertrie popularity was classified as not popular.
We found that hypertrie 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
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.