sparse-bitfield

npmv3.0.3

Bitfield that allocates a series of small buffers to support sparse bits without allocating a massive buffer

Not recommended for new projects

No — sparse-bitfield should not be adopted for new projects. Last published 3476 days ago.

AAdoption: grade A, Excellent.
7.3M downloads per week and 1 known dependents.
FMaintenance: grade F, Failing.
Last published 3476 days ago.
AWeight: grade A, Excellent.
Pulls in 1 transitive package, about 7.9 KB installed.
BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding sparse-bitfield to a project.

Direct dependencies

Runtime packages this one declares itself.

Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

7.9 KB

Install size

Unpacked size of this package plus its entire runtime tree.

Tree depth

Longest resolved dependency chain below this package.

Licenses in the dependency tree

MIT

Every license you inherit by installing sparse-bitfield, not just its own. Check this before a legal review, not after.

Compatibility

Node.js: No constraint declared
Module format: CommonJS only
TypeScript: No bundled types
Install scripts: None

Quick start

A usage example from the sparse-bitfield README.

jsFull README ↗

var bitfield = require('sparse-bitfield')
var bits = bitfield()

bits.set(0, true) // set first bit
bits.set(1, true) // set second bit
bits.set(1000000000000, true) // set the 1.000.000.000.000th bit

Dependencies

Declared by sparse-bitfield v3.0.3. Runtime dependencies are installed with the package; dev dependencies are not.

Runtime (1)

memory-pager ^1.0.2

Dev (3)

buffer-alloc ^1.1.0standard ^9.0.0tape ^4.6.3

Used by

Popular packages that depend on sparse-bitfield.

@mongodb-js/saslprepnpm

SASLprep: Stringprep Profile for User Names and Passwords, rfc4013

↓ 0/wk◈ 1 dependents⚖ MITTS

Relationship graph

Dependencies (left) and dependents (right) of sparse-bitfield.

sparse-bitfield dependencies dependents

Frequently installed together

eslintnpm

An AST-based pattern checker for JavaScript.

↓ 138.4M/wk◈ 279 dependents⚖ MITTS

prettiernpm

Prettier is an opinionated code formatter

↓ 114.2M/wk◈ 159 dependents⚖ MITTS

@types/nodenpm

TypeScript definitions for node

↓ 0/wk◈ 327 dependents⚖ MITTS

chainpm

BDD/TDD assertion library for node.js and the browser. Test framework agnostic.

↓ 0/wk◈ 57 dependents⚖ MIT

@types/chainpm

TypeScript definitions for chai

↓ 0/wk◈ 19 dependents⚖ MITTS

Release history

No releases in the last two years, typically about 4 days apart.

Recent versions of sparse-bitfield
Version	Published	Size	License
3.0.3latest	9 years ago	—	MIT
3.0.2	9 years ago	—	MIT
3.0.1	9 years ago	—	MIT
3.0.0	9 years ago	—	MIT
2.2.0	9 years ago	—	MIT
2.1.0	9 years ago	—	MIT
2.0.2	9 years ago	—	MIT
2.0.1	9 years ago	—	MIT
2.0.0	9 years ago	—	MIT
1.0.0	10 years ago	—	MIT

Overview

sparse-bitfield is an npm package that bitfield that allocates a series of small buffers to support sparse bits without allocating a massive buffer. It is extremely widely used, with about 7.3M downloads per week and 1 known dependents in the graph. The latest version is 3.0.3, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need bitfield that allocates a series of small buffers to support sparse bits without allocating a massive buffer and value a battle-tested, widely-adopted solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

Large, well-established user base (7.3M weekly downloads).
Clear open-source license (MIT).

Cons

No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

mafintosh

Frequently asked questions

Should I use sparse-bitfield?

No — sparse-bitfield should not be adopted for new projects. Last published 3476 days ago.

How do I install sparse-bitfield?

Run `npm install sparse-bitfield` to add sparse-bitfield to your npm project.

How many dependencies does sparse-bitfield have?

sparse-bitfield declares 4 direct dependencies and pulls in 1 packages in total once its runtime tree is resolved totalling about 7.9 KB on disk.

What license is sparse-bitfield released under?

sparse-bitfield is distributed under the MIT license.

How popular is sparse-bitfield?

sparse-bitfield has approximately 7,347,897 downloads per week and 1 known dependent packages.

Is sparse-bitfield still maintained?

The most recent release of sparse-bitfield (v3.0.3) was published 9 years ago.

Does sparse-bitfield run install scripts?

No. sparse-bitfield does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.