Is @reacting/purist safe to use?

@reacting/purist has no known vulnerabilities on the latest version (0.1.0). DepScope rates its health at 39/100 (critical risk).

What is the latest version of @reacting/purist?

The latest version of @reacting/purist is 0.1.0, released 2018-08-01.

Does @reacting/purist have known vulnerabilities?

No known vulnerabilities on the latest version of @reacting/purist.

Is @reacting/purist deprecated?

No, @reacting/purist is actively maintained. Latest release: 0.1.0 (2018-08-01).

What are alternatives to @reacting/purist?

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

What license does @reacting/purist use?

@reacting/purist is licensed under MIT .

@reacting/purist

npmv0.1.0

Utilizes FormidableLabs `react-fast-compare` to provide a custom PureComponent wrapper that is magnitudes faster than React.PureComponent.

License MIT permissive7 versions1 maintainers1 deps

/ 100

Health

use with caution

@reacting/[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

Dependencies (1)

react-fast-compare

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@reacting/purist