![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
This module enables sequential bitwise parsing of binary Buffers, using a simple .readBits(n)
interface.
var bitparser = require('bitparser');
var buffer = new Buffer([0xDE, 0xAD, 0xBE, 0xEF]);
var bp = bitparser(buffer);
// read first 5 bits
var first = bp.readBits(5);
// read next 12 bits
var second = bp.readBits(12);
// skip the next 14 bits
bp.skipBits(14);
// read final bit
var final = bp.read1Bit();
console.log('bits:', [first, second, final]);
Output:
bits: [ 27, 3419, 1 ]
npm install bitparser
Create a BitParser
for the buffer
of type Buffer
, starting at index 0.
Note: Due to internal caching, the result will be undefined if the buffer is modified during parsing.
Read next 1 to 32 bits from the buffer, as specified by n
, advancing the index.
Note: n
is not checked for validity, and any read past the end of the buffer returns undefined bits.
Read 1 bit from the buffer, advancing the index. For optimal performance, use this instead of .readBits(1)
.
Skip next n
bits from the buffer by advancing the index. n
can be any amount of bits, including negative values which will rewind the parser.
Read len
bytes, returning a Buffer
object with the contents.
Note: The returned buffer is only valid as long as the original buffer is not modified.
Reset the parser, starting at index 0.
(BSD 2-Clause License)
Copyright (c) 2013-2015, Gil Pedersen <gpdev@gpost.dk> All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
FAQs
Optimized parsing of bits from a Buffer
The npm package bitparser receives a total of 4 weekly downloads. As such, bitparser popularity was classified as not popular.
We found that bitparser 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
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.