Is coverage-blamer safe to use?

coverage-blamer has no known vulnerabilities on the latest version (0.1.9). DepScope rates its health at 42/100 (high risk).

What is the latest version of coverage-blamer?

The latest version of coverage-blamer is 0.1.9, released 2016-06-16.

Does coverage-blamer have known vulnerabilities?

No known vulnerabilities on the latest version of coverage-blamer.

Is coverage-blamer deprecated?

No, coverage-blamer is actively maintained. Latest release: 0.1.9 (2016-06-16).

What are alternatives to coverage-blamer?

Popular alternatives to coverage-blamer in npm include: ?., ansi-styles, brace-expansion, strip-ansi, lru-cache.

What license does coverage-blamer use?

coverage-blamer is licensed under MIT.

coverage-blamer

npmv0.1.9

coverage-blamer is tool for get information about authors of uncovered code

License MITpermissive10 versions1 maintainers12 deps29 weekly dl

kucherenko/coverage-blamer

/ 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

Bundle & TypeScript

📦

Bundle Size

0.2 KBminified

0.2 KB gzipped

12 direct dependencies

side effects

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (12)

blamer bluebird cli-table commander glob jade kouto-swiss lcov-parse lodash markdown-table mkdirp stylus

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/coverage-blamer