enzyme-adapter-react-15
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): ljharb is the well-known legitimate maintainer of the enzyme ecosystem; the transition from intelligibabble is a documented handoff, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): ljharb is a highly trusted npm maintainer (4062 approved packages); addition is a legitimate maintainer transition for the enzyme project. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is a legitimate declared dependency used in config/build context; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): prop-types is a legitimate declared dependency; phantom-dep false positive for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.4.4 | 5 / 17 | |
| 1.4.3 | 5 / 15 | |
| 1.4.2 | 5 / 15 | |
| 1.4.1 | 5 / 12 | |
| 1.4.0 | 5 / 12 | |
| 1.3.1 | 5 / 12 | |
| 1.3.0 | 5 / 12 | |
| 1.2.0 | 5 / 12 | |
| 1.1.1 | 5 / 12 | |
| 1.1.0 | 5 / 12 | |
| 1.0.6 | 5 / 12 | |
| 1.0.5 | 5 / 11 | |
| 1.0.4 | 5 / 7 | |
| 1.0.3 | 5 / 6 | |
| 1.0.2 | 6 / 5 | |
| 1.0.1 | 5 / 5 | |
| 1.0.0 | 5 / 5 |
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
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.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.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.