Is @bcoe/v8-coverage safe to use?

@bcoe/v8-coverage has no known vulnerabilities on the latest version (1.0.2). DepScope rates its health at 44/100 (high risk).

What is the latest version of @bcoe/v8-coverage?

The latest version of @bcoe/v8-coverage is 1.0.2, released 2025-01-15.

Does @bcoe/v8-coverage have known vulnerabilities?

No known vulnerabilities on the latest version of @bcoe/v8-coverage.

Is @bcoe/v8-coverage deprecated?

No, @bcoe/v8-coverage is actively maintained. Latest release: 1.0.2 (2025-01-15).

What are alternatives to @bcoe/v8-coverage?

Popular alternatives to @bcoe/v8-coverage in npm include: debug, chalk, picomatch, source-map, has-flag.

What license does @bcoe/v8-coverage use?

@bcoe/v8-coverage is licensed under MIT.

@bcoe/v8-coverage

npmv1.0.2

Helper functions for V8 coverage files.

License MITpermissive8 versions1 maintainers0 deps

git://github.com/bcoe/v8-coverage

/ 100

Health

safe to use

@bcoe/[email protected] is safe to use (health: 44/100)

Health breakdown0 – 100

5/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

8.1 KBminified

2.7 KB gzipped

0 direct dependencies

side effectsscoped

🌟

TypeScript

0/10untyped

No type definitions available

Quality signals

OSS Criticality

0.76critical

Download trend

stable(0%)

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@bcoe/v8-coverage