use-deep-compare-effect 1.2.0

It's react's useEffect hook, except using deep comparison on the inputs, not reference equality

use-deep-compare-effect@1.2.0 was published on 2019-04-07. Its manifest declares 2 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is > 4.

All use-deep-compare-effect versions · Permanent reference to 1.2.0 · Latest release

Package specifications

Version1.2.0
License declarationMIT
Published2019-04-07T00:45:09.431Z
Node.js requirement> 4
Type declarationsNot declared
Runtime dependency count2
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size23.36 KiB
Published file count10
Package typeNot declared
ES module entrydist/use-deep-compare-effect.esm.js
Default entrydist/use-deep-compare-effect.cjs.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies2
Repository stars1914
Repository forks88

Install use-deep-compare-effect 1.2.0

npm install use-deep-compare-effect@1.2.0
pnpm add use-deep-compare-effect@1.2.0
yarn add use-deep-compare-effect@1.2.0

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Code-Review6/10 — Found 12/19 approved changesets -- score normalized to 6
Binary-Artifacts10/10 — no binaries found in the repo
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness