Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
functional-red-black-tree
Advanced tools
The functional-red-black-tree npm package provides an implementation of a functional (immutable) red-black tree, a type of self-balancing binary search tree. It allows for efficient insertion, deletion, and lookup of elements while maintaining a balanced tree structure. The functional aspect means that instead of modifying the tree in place, operations return a new tree, preserving the original structure.
Insertion
This feature allows for the insertion of a key-value pair into the tree. The operation returns a new tree with the element added, maintaining the original tree unchanged.
const RBT = require('functional-red-black-tree');
let tree = RBT();
tree = tree.insert(1, 'value');
Deletion
This feature enables the removal of an element by its key from the tree. Similar to insertion, it returns a new tree with the specified element removed, leaving the original tree intact.
tree = tree.remove(1);
Lookup
This feature allows for the retrieval of a value by its key from the tree. It returns the value associated with the key if it exists, or undefined if the key is not found in the tree.
const value = tree.get(1);
The bintrees package provides a collection of binary tree data structures, including a binary search tree and a red-black tree. Unlike functional-red-black-tree, bintrees does not focus on immutability, allowing in-place modifications of the tree.
The immutable package offers a wide range of immutable data structures, including Lists, Stacks, Maps, and more. While it does not provide a red-black tree specifically, its focus on immutability and efficient data structures makes it a relevant alternative for applications requiring immutable data handling.
A fully persistent red-black tree written 100% in JavaScript. Works both in node.js and in the browser via browserify.
Functional (or fully presistent) data structures allow for non-destructive updates. So if you insert an element into the tree, it returns a new tree with the inserted element rather than destructively updating the existing tree in place. Doing this requires using extra memory, and if one were naive it could cost as much as reallocating the entire tree. Instead, this data structure saves some memory by recycling references to previously allocated subtrees. This requires using only O(log(n)) additional memory per update instead of a full O(n) copy.
Some advantages of this is that it is possible to apply insertions and removals to the tree while still iterating over previous versions of the tree. Functional and persistent data structures can also be useful in many geometric algorithms like point location within triangulations or ray queries, and can be used to analyze the history of executing various algorithms. This added power though comes at a cost, since it is generally a bit slower to use a functional data structure than an imperative version. However, if your application needs this behavior then you may consider using this module.
npm install functional-red-black-tree
Here is an example of some basic usage:
//Load the library
var createTree = require("functional-red-black-tree")
//Create a tree
var t1 = createTree()
//Insert some items into the tree
var t2 = t1.insert(1, "foo")
var t3 = t2.insert(2, "bar")
//Remove something
var t4 = t3.remove(1)
var createTree = require("functional-red-black-tree")
var tree = createTree([compare])
Creates an empty functional tree
compare
is an optional comparison function, same semantics as array.sort()Returns An empty tree ordered by compare
tree.keys
A sorted array of all the keys in the tree
tree.values
An array array of all the values in the tree
tree.length
The number of items in the tree
tree.get(key)
Retrieves the value associated to the given key
key
is the key of the item to look upReturns The value of the first node associated to key
tree.insert(key, value)
Creates a new tree with the new pair inserted.
key
is the key of the item to insertvalue
is the value of the item to insertReturns A new tree with key
and value
inserted
tree.remove(key)
Removes the first item with key
in the tree
key
is the key of the item to removeReturns A new tree with the given item removed if it exists
tree.find(key)
Returns an iterator pointing to the first item in the tree with key
, otherwise null
.
tree.ge(key)
Find the first item in the tree whose key is >= key
key
is the key to search forReturns An iterator at the given element.
tree.gt(key)
Finds the first item in the tree whose key is > key
key
is the key to search forReturns An iterator at the given element
tree.lt(key)
Finds the last item in the tree whose key is < key
key
is the key to search forReturns An iterator at the given element
tree.le(key)
Finds the last item in the tree whose key is <= key
key
is the key to search forReturns An iterator at the given element
tree.at(position)
Finds an iterator starting at the given element
position
is the index at which the iterator gets createdReturns An iterator starting at position
tree.begin
An iterator pointing to the first element in the tree
tree.end
An iterator pointing to the last element in the tree
tree.forEach(visitor(key,value)[, lo[, hi]])
Walks a visitor function over the nodes of the tree in order.
visitor(key,value)
is a callback that gets executed on each node. If a truthy value is returned from the visitor, then iteration is stopped.lo
is an optional start of the range to visit (inclusive)hi
is an optional end of the range to visit (non-inclusive)Returns The last value returned by the callback
tree.root
Returns the root node of the tree
Each node of the tree has the following properties:
node.key
The key associated to the node
node.value
The value associated to the node
node.left
The left subtree of the node
node.right
The right subtree of the node
iter.key
The key of the item referenced by the iterator
iter.value
The value of the item referenced by the iterator
iter.node
The value of the node at the iterator's current position. null
is iterator is node valid.
iter.tree
The tree associated to the iterator
iter.index
Returns the position of this iterator in the sequence.
iter.valid
Checks if the iterator is valid
iter.clone()
Makes a copy of the iterator
iter.remove()
Removes the item at the position of the iterator
Returns A new binary search tree with iter
's item removed
iter.update(value)
Updates the value of the node in the tree at this iterator
Returns A new binary search tree with the corresponding node updated
iter.next()
Advances the iterator to the next position
iter.prev()
Moves the iterator backward one element
iter.hasNext
If true, then the iterator is not at the end of the sequence
iter.hasPrev
If true, then the iterator is not at the beginning of the sequence
(c) 2013 Mikola Lysenko. MIT License
FAQs
A fully persistent balanced binary search tree
The npm package functional-red-black-tree receives a total of 10,702,295 weekly downloads. As such, functional-red-black-tree popularity was classified as popular.
We found that functional-red-black-tree 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
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.