enzyme-adapter-react-helper
JavaScript Testing utilities for React
Supply chain provenance
Status for the latest visible version.
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
Keywords
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 2017 and is a well-documented legitimate handoff within the enzyme/Airbnb ecosystem. Not a takeover signal. | ai | |
| phantom-deps | phantom-dep:install-peerdeps | AI (phantom-deps): install-peerdeps is used as a CLI tool via the bin entry, not imported directly. Expected usage pattern for this dependency type. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): ljharb is the well-known enzymejs maintainer; removal of prior maintainers reflects consolidation under the project's primary steward, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Enzyme is a legacy/maintenance-mode package; infrequent releases by the known maintainer ljharb are expected and not indicative of account takeover. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.3.10 | 7 / 17 | |
| 1.3.9 | 7 / 16 | |
| 1.3.8 | 7 / 16 | |
| 1.3.7 | 7 / 13 | |
| 1.3.6 | 7 / 13 | |
| 1.3.5 | 7 / 13 | |
| 1.3.4 | 7 / 13 | |
| 1.3.3 | 7 / 13 | |
| 1.3.2 | 7 / 13 | |
| 1.3.1 | 7 / 13 | |
| 1.3.0 | 7 / 13 | |
| 1.2.3 | 6 / 12 | |
| 1.2.2 | 5 / 12 | |
| 1.2.1 | 5 / 12 | |
| 1.2.0 | 5 / 11 | |
| 1.1.0 | 4 / 10 | |
| 1.0.3 | 4 / 10 | |
| 1.0.2 | 4 / 10 |
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2017-11-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
2 findingsThis version was published by a different npm account than previous versions on 2017-11-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.