Is sparse-bitfield safe to use?

sparse-bitfield has no known vulnerabilities on the latest version (3.0.3). DepScope rates its health at 42/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.

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

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

Popular alternatives to sparse-bitfield in npm include: minimatch, wrap-ansi, @types/node, eslint-visitor-keys, ajv.

sparse-bitfield is licensed under MIT.

npmv3.0.3

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

License MITpermissive10 versions1 maintainers1 deps

/ 100

Health

safe to use

[email protected] is safe to use (health: 42/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

🌟

7/10typed

Types from @types/sparse-bitfield (DefinitelyTyped)

Quality signals

Publish security

npm signed

Dependencies (1)

API access

Get this data programmatically — free, no authentication.

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