Is @ohze/rangefix safe to use?

@ohze/rangefix has no known vulnerabilities on the latest version (0.2.6). DepScope rates its health at 39/100 (critical risk).

What is the latest version of @ohze/rangefix?

The latest version of @ohze/rangefix is 0.2.6, released 2019-03-18.

Does @ohze/rangefix have known vulnerabilities?

No known vulnerabilities on the latest version of @ohze/rangefix.

Is @ohze/rangefix deprecated?

No, @ohze/rangefix is actively maintained. Latest release: 0.2.6 (2019-03-18).

What are alternatives to @ohze/rangefix?

Popular alternatives to @ohze/rangefix in npm include: ?, semver, ansi-styles, debug, minimatch.

What license does @ohze/rangefix use?

@ohze/rangefix is licensed under MIT.

@ohze/rangefix

npmv0.2.6

Workaround for browser bugs in Range.prototype.getClientRects and Range.prototype.getBoundingClientRect.

License MITpermissive1 versions1 maintainers0 deps

ohze/rangefix

/ 100

Health

use with caution

@ohze/[email protected] low health (39/100) — consider alternatives

Moderate health score (39/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/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

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@ohze/rangefix