enzyme-adapter-react-16
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): Legitimate maintainer transition from intelligibabble (Leland Richardson) to ljharb (Jordan Harb), well-known npm maintainer who took over enzyme project. | ai | |
| provenance | no-provenance | AI (provenance): Package published in 2017, before Sigstore provenance existed. Stable for this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is a declared dependency used transitively or in build output; not suspicious for this package. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): prop-types is a declared dependency used transitively or in build output; expected for a React adapter. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): ljharb remains the publisher; brieb addition is a routine roster update for this well-established enzyme ecosystem package. | ai | |
| phantom-deps | phantom-dep:object.values | AI (phantom-deps): object.values is explicitly declared in dependencies and is a legitimate runtime dep; phantom detection is a false positive here. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of noratarano alongside addition of brieb is a routine maintainer rotation; ljharb (trusted publisher) remains in control. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Enzyme is in maintenance mode; long gaps between releases are expected. Trusted publisher ljharb continues to maintain the package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): hasown is a well-known ljharb-maintained successor to 'has'; this is a routine dependency modernization, not a suspicious addition. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 1.15.8 | 9 / 17 | |
| 1.15.7 | 9 / 17 | |
| 1.15.6 | 9 / 15 | |
| 1.15.5 | 9 / 15 | |
| 1.15.4 | 9 / 15 | |
| 1.15.3 | 9 / 15 | |
| 1.15.2 | 9 / 12 | |
| 1.15.1 | 9 / 12 | |
| 1.15.0 | 9 / 12 | |
| 1.14.0 | 8 / 12 | |
| 1.13.2 | 8 / 12 | |
| 1.13.1 | 8 / 12 | |
| 1.13.0 | 7 / 12 | |
| 1.12.1 | 7 / 12 | |
| 1.12.0 | 7 / 12 | |
| 1.11.2 | 7 / 12 | |
| 1.11.1 | 7 / 12 | |
| 1.11.0 | 7 / 12 | |
| 1.10.0 | 6 / 12 | |
| 1.9.1 | 7 / 12 | |
| 1.9.0 | 7 / 12 | |
| 1.8.0 | 7 / 12 | |
| 1.7.1 | 7 / 12 | |
| 1.7.0 | 7 / 12 | |
| 1.6.0 | 7 / 12 | |
| 1.5.0 | 7 / 12 | |
| 1.4.0 | 7 / 12 | |
| 1.3.1 | 7 / 12 | |
| 1.3.0 | 7 / 12 | |
| 1.2.0 | 8 / 12 | |
| 1.1.1 | 7 / 10 | |
| 1.1.0 | 6 / 10 | |
| 1.0.4 | 6 / 10 | |
| 1.0.3 | 6 / 6 | |
| 1.0.2 | 6 / 5 | |
| 1.0.1 | 5 / 5 | |
| 1.0.0 | 5 / 5 |
v1.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package 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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage 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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
2 findingsThis version was published by a different npm account than previous versions on 2017-10-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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.