Is yet-another-eslint-blame safe to use?

yet-another-eslint-blame has no known vulnerabilities on the latest version (0.0.3). DepScope rates its health at 36/100 (critical risk).

What is the latest version of yet-another-eslint-blame?

The latest version of yet-another-eslint-blame is 0.0.3, released 2022-03-03.

Does yet-another-eslint-blame have known vulnerabilities?

No known vulnerabilities on the latest version of yet-another-eslint-blame.

Is yet-another-eslint-blame deprecated?

No, yet-another-eslint-blame is actively maintained. Latest release: 0.0.3 (2022-03-03).

What are alternatives to yet-another-eslint-blame?

Popular alternatives to yet-another-eslint-blame in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does yet-another-eslint-blame use?

License information for yet-another-eslint-blame is not declared in the registry metadata.

yet-another-eslint-blame

npmv0.0.3

Yet another eslint blame (might) with better adaptability. The input is eslint's output with json format (You can see it [here](https://eslint.org/docs/user-guide/formatters/#json)). And it's will run git blame for each eslint report.

3 versions1 maintainers3 deps79 weekly dl

kwai-explore/yet-another-eslint-blame

/ 100

Health

use with caution

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

Moderate health score (36/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

9/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (3)

get-stdin git-blame-line yargs

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/yet-another-eslint-blame