← Home

assertion-error

npm Repository Homepage

Error constructor for test and validation frameworks that implements standardized AssertionError specification.

7
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

chaijskeithamus

Keywords

testassertionassertion-error

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-takeover AI (maintainer-change): Legitimate transfer from jakeluer (Jake Luer) to chaijs org account in 2016; repo URL confirms chaijs ownership. Stable for this package. ai
maintainer-change maintainer-removed AI (maintainer-change): jakeluer replaced by chaijs org account; well-documented legitimate maintainer transition for the Chai.js ecosystem. ai
provenance publisher-changed AI (provenance): Publisher change from chaijs to chai is a legitimate transition within the same Chai project organization. ai
maintainer-change maintainer-added AI (maintainer-change): chai is the canonical maintainer account for the chaijs ecosystem; legitimate org transition. ai

Versions (showing 7 of 7)

Version Deps Published
2.0.1 0 / 0
2.0.0 0 / 1
1.1.0 0 / 2
1.0.2 0 / 1
1.0.1 0 / 1
1.0.0 0 / 1
0.1.0 0 / 1

v2.0.0

2 findings
HIGH Publisher changed: chaijs → chai (on 2021-10-05) provenance

This version was published by a different npm account than previous versions on 2021-10-05. 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.

v1.1.0

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (jakeluer) were replaced by new maintainers (chaijs). This is a strong signal of a potential package hijack and requires careful review.

LOW No provenance attestation provenance

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

INFO Publisher changed: jakeluer → chaijs (on 2018-01-07) provenance

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

v1.0.2

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (jakeluer) were replaced by new maintainers (chaijs). This is a strong signal of a potential package hijack and requires careful review.

LOW No provenance attestation provenance

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

INFO Publisher changed: jakeluer → chaijs (on 2016-06-06) provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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