</>PackageGraphPackageGraph

deep-equal

npmv2.2.3

node's assert.deepEqual algorithm

Adopt with care

deep-equal is usable, with caveats. Last published 1036 days ago. Pulls in 50 transitive packages, about 860 KB installed (at least — some of the tree is still being crawled).

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • DMaintenance: grade D, Poor — a real concern.

    Last published 1036 days ago.

  • CWeight: grade C, Fair — worth a look.

    Pulls in 50 transitive packages, about 860 KB installed (at least — some of the tree is still being crawled).

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding deep-equal to a project.

18
Direct dependencies

Runtime packages this one declares itself.

50
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

860 KB
Install size

Unpacked size of this package plus its entire runtime tree.

3
Tree depth

Longest resolved dependency chain below this package.

Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.

Licenses in the dependency tree

MIT

Every license you inherit by installing deep-equal, not just its own. Check this before a legal review, not after.

Compatibility

Node.js
node >= 0.4
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the deep-equal README.

var equal = require('deep-equal');
console.dir([
    equal(
        { a : [ 2, 3 ], b : [ 4 ] },
        { a : [ 2, 3 ], b : [ 4 ] }
    ),
    equal(
        { x : 5, y : [6] },
        { x : 5, y : 6 }
    )
]);

deep-equal vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
deep-equalthis page06MIT2 years ago
deep-is01MIT1 day ago
react-fast-compare01MIT1 day ago
shallowequal01MIT1 day ago
diff124.1M4BSD-3-Clause1 day ago
object-is21.5M1MIT1 day ago

Dependencies

Declared by deep-equal v2.2.3. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (16)

@ljharb/eslint-config ^21.1.0aud ^2.0.3auto-changelog ^2.4.0available-typed-arrays ^1.0.5eslint =8.8.0for-each ^0.3.3has-proto ^1.0.1has-symbols ^1.0.3has-typed-arrays ^1.0.1in-publish ^2.0.1npmignore ^0.3.0nyc ^10.3.2object.getownpropertydescriptors ^2.1.7safe-publish-latest ^2.0.0semver ^6.3.1tape ^5.7.2

Used by

Popular packages that depend on deep-equal.

Relationship graph

Dependencies (left) and dependents (right) of deep-equal.

Frequently installed together

Release history

No releases in the last two years, typically about 74 days apart.

Recent versions of deep-equal
VersionPublishedSizeLicense
2.2.3latest2 years ago88 KBMIT
1.1.22 years ago74 KBMIT
2.2.23 years ago81 KBMIT
2.2.13 years ago79 KBMIT
2.2.03 years ago78 KBMIT
2.1.03 years ago75 KBMIT
2.0.55 years ago73 KBMIT
2.0.46 years ago66 KBMIT
2.0.36 years ago64 KBMIT
2.0.26 years ago63 KBMIT
2.0.16 years ago52 KBMIT
1.1.16 years ago26 KBMIT
1.1.07 years ago25 KBMIT
1.0.111 years agoMIT
1.0.011 years agoMIT

Overview

deep-equal is an npm package that node's assert.deepEqual algorithm. It has 6 known dependents in the graph. The latest version is 2.2.3, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need node's assert.deepEqual algorithm and value a focused solution.

When not to use it

Consider an alternative if you need to minimize your dependency tree, have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Clear open-source license (MIT).

Cons

  • Large dependency tree (34 direct dependencies) increases install size and audit surface.
  • No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

Keywords

Funding

Frequently asked questions

Should I use deep-equal?

deep-equal is usable, with caveats. Last published 1036 days ago. Pulls in 50 transitive packages, about 860 KB installed (at least — some of the tree is still being crawled).

How do I install deep-equal?

Run `npm install deep-equal` to add deep-equal to your npm project.

How many dependencies does deep-equal have?

deep-equal declares 34 direct dependencies and pulls in 50 packages in total once its runtime tree is resolved totalling about 860 KB on disk.

What license is deep-equal released under?

deep-equal is distributed under the MIT license.

How popular is deep-equal?

npm does not publish download counts. Within PackageGraph's crawl, 6 known packages depend on deep-equal.

Is deep-equal still maintained?

The most recent release of deep-equal (v2.2.3) was published 2 years ago.

Does deep-equal run install scripts?

No. deep-equal does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.