Is @vipzhichengfork/node-readability safe to use?

@vipzhichengfork/node-readability has no known vulnerabilities on the latest version (1.0.5). DepScope rates its health at 42/100 (high risk).

What is the latest version of @vipzhichengfork/node-readability?

The latest version of @vipzhichengfork/node-readability is 1.0.5, released 2020-06-16.

Does @vipzhichengfork/node-readability have known vulnerabilities?

No known vulnerabilities on the latest version of @vipzhichengfork/node-readability.

Is @vipzhichengfork/node-readability deprecated?

No, @vipzhichengfork/node-readability is actively maintained. Latest release: 1.0.5 (2020-06-16).

What are alternatives to @vipzhichengfork/node-readability?

Popular alternatives to @vipzhichengfork/node-readability in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does @vipzhichengfork/node-readability use?

License information for @vipzhichengfork/node-readability is not declared in the registry metadata.

@vipzhichengfork/node-readability

npmv1.0.5

Turning any web page into a clean view.

6 versions1 maintainers4 deps138 weekly dl

vipzhichengfork/readability

/ 100

Health

use with caution

@vipzhichengfork/[email protected] low health (42/100) — consider alternatives

Moderate health score (42/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

3/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (4)

encoding jsdom minimist request

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@vipzhichengfork/node-readability