← Home

deep-eql

npm Repository Homepage

Improved deep equality testing for Node.js and the browser.

23
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

chaijs

Keywords

chai utildeep equalobject equaltesting

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate transition from 'chai' to 'chaijs' org account within the Chai.js ecosystem; keithamus is a known long-standing contributor. ai
maintainer-change maintainer-added AI (maintainer-change): keithamus (Keith Cirkel) is a known Chai.js core contributor listed in package.json contributors. ai
maintainer-change maintainer-removed AI (maintainer-change): Routine org transition from individual 'chai' account to 'chaijs' org account. ai

Versions (showing 23 of 23)

Version Deps Published
5.0.2 0 / 14
5.0.1 0 / 14
5.0.0 1 / 14
4.1.4 1 / 20
4.1.3 1 / 20
4.1.2 1 / 20
4.1.1 1 / 23
4.1.0 1 / 23
4.0.1 1 / 22
4.0.0 1 / 26
3.0.1 1 / 26
3.0.0 1 / 26
2.0.2 1 / 26
2.0.1 1 / 26
2.0.0 1 / 26
1.0.3 1 / 26
1.0.2 1 / 26
1.0.1 1 / 26
1.0.0 1 / 26
0.1.3 1 / 8
0.1.2 1 / 8
0.1.1 1 / 8
0.1.0 1 / 8

v5.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.1

2 findings
HIGH Publisher changed: chai → chaijs (on 2023-10-25) provenance

This version was published by a different npm account than previous versions on 2023-10-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.0

2 findings
HIGH Publisher changed: chai → chaijs (on 2023-10-18) provenance

This version was published by a different npm account than previous versions on 2023-10-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: chaijs → chai (on 2022-02-28) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-02-28. This could indicate a legitimate maintainer transition or an account compromise.

v4.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.