Is sparse-bitfield safe to use?

sparse-bitfield has no known vulnerabilities on the latest version (3.0.3). DepScope rates its health at 59/100 (high risk).

What is the latest version of sparse-bitfield?

The latest version of sparse-bitfield is 3.0.3, released 2017-03-05.

Does sparse-bitfield have known vulnerabilities?

No known vulnerabilities on the latest version of sparse-bitfield.

Is sparse-bitfield deprecated?

No, sparse-bitfield is actively maintained. Latest release: 3.0.3 (2017-03-05).

What are alternatives to sparse-bitfield?

Popular alternatives to sparse-bitfield in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does sparse-bitfield use?

sparse-bitfield is licensed under MIT.

sparse-bitfield

npmv3.0.3

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

License MITpermissive10 versions1 maintainers1 deps7,715,667 weekly dl

mafintosh/sparse-bitfield

/ 100

Health

use with caution

[email protected] low health (59/100) — consider alternatives

Moderate health score (59/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

17/20

popularity

25/25

security

15/15

maturity

2/15

community

0/15

popularity_floor

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

7/10typed

Types from @types/sparse-bitfield (DefinitelyTyped)

Quality signals

Publish security

npm signed

Health History

Dependency Tree

License Audit

Dependencies (1)

memory-pager

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/sparse-bitfield