enzyme-adapter-utils — Greenflagged

JavaScript Testing utilities for React

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

briebairbnbenglencioniljharbintelligibabble

Keywords

javascriptshallow renderingshallowRendertestreactjsreactfluxtestingtest utilsassertion helperstddmocha

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): The ljharb→airbnb transition occurred in Nov 2017 and is a well-documented legitimate org consolidation for the enzyme ecosystem. Stable for this package.	ai	2026/04/24
phantom-deps	phantom-dep:lodash	AI (phantom-deps): Lodash is a declared runtime dependency; the phantom-dep finding is a false positive for this package.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): hasown is a direct successor to 'has', authored by the same publisher (ljharb). Replacing 'has' with 'hasown' is a documented, routine migration pattern in ljharb's packages.	ai	2026/04/23

Versions (showing 25 of 25)

Version	Deps	Published
1.14.2	7 / 16	2024-02-10
1.14.1	7 / 16	2022-11-04
1.14.0	7 / 14	2020-12-10
1.13.1	6 / 14	2020-08-07
1.13.0	6 / 11	2019-12-19
1.12.1	6 / 11	2019-10-10
1.12.0	6 / 11	2019-05-06
1.11.0	6 / 11	2019-04-05
1.10.1	5 / 11	2019-03-09
1.10.0	5 / 11	2019-01-22
1.9.1	4 / 11	2019-01-04
1.9.0	4 / 11	2018-11-08
1.8.1	3 / 11	2018-10-04
1.8.0	3 / 11	2018-09-05
1.7.0	3 / 11	2018-09-04
1.6.1	3 / 11	2018-08-30
1.6.0	3 / 11	2018-08-24
1.5.0	3 / 11	2018-08-06
1.4.0	2 / 11	2018-07-09
1.3.0	3 / 10	2017-12-18
1.2.0	3 / 10	2017-11-22
1.1.1	3 / 10	2017-11-05
1.1.0	3 / 6	2017-11-02
1.0.1	3 / 4	2017-10-03
1.0.0	3 / 4	2017-09-26

v1.14.2

1 finding

LOW No provenance attestation provenance

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

v1.14.1

1 finding

LOW No provenance attestation provenance

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

v1.14.0

1 finding

LOW No provenance attestation provenance

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

v1.13.1

1 finding

LOW No provenance attestation provenance

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

v1.13.0

1 finding

LOW No provenance attestation provenance

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

v1.12.1

1 finding

LOW No provenance attestation provenance

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

v1.12.0

1 finding

LOW No provenance attestation provenance

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

v1.11.0

1 finding

LOW No provenance attestation provenance

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

v1.10.1

1 finding

LOW No provenance attestation provenance

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

v1.10.0

1 finding

LOW No provenance attestation provenance

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

v1.9.1

1 finding

LOW No provenance attestation provenance

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

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.1

1 finding

LOW No provenance attestation provenance

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

v1.8.0

1 finding

LOW No provenance attestation provenance

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

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.1

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.0

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: airbnb → ljharb (on 2017-12-18) provenance

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

v1.2.0

2 findings

HIGH Publisher changed: ljharb → airbnb (on 2017-11-22) provenance

This version was published by a different npm account than previous versions on 2017-11-22. 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.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

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: intelligibabble → ljharb (on 2017-11-02) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-11-02. 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. Only ~12% of npm packages have provenance, so this is common but not ideal.