enzyme-to-json
convert enzyme wrapper to a format compatible with Jest snapshot
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 | missing-githead | AI (provenance): Publisher is the original author; missing gitHead is a publish-environment artifact, not a security signal for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): trayio removal is consistent with author leaving Tray.io; normal maintainer cleanup, not a takeover. | ai | |
| provenance | publisher-changed | AI (provenance): adriantoine is the original author per package.json, GitHub repo, and bugs email. This is the author reclaiming publish rights. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): react-is is a first-party React package, appropriate for a React/Enzyme serialization library. | ai | |
| provenance | no-provenance | AI (provenance): Published in Jan 2020, before npm provenance support existed. Expected for this era. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 3.6.2 | 3 / 25 | |
| 3.6.1 | 3 / 25 | |
| 3.6.0 | 2 / 25 | |
| 3.5.0 | 2 / 25 | |
| 3.4.4 | 2 / 25 | |
| 3.4.3 | 1 / 27 | |
| 3.4.2 | 1 / 27 | |
| 3.4.1 | 1 / 27 | |
| 3.4.0 | 1 / 27 | |
| 3.3.5 | 1 / 27 | |
| 3.3.4 | 1 / 26 | |
| 3.3.3 | 1 / 26 | |
| 3.3.1 | 1 / 26 | |
| 3.3.0 | 1 / 26 | |
| 3.2.2 | 1 / 26 | |
| 3.2.1 | 1 / 26 | |
| 3.2.0 | 1 / 26 | |
| 3.1.4 | 1 / 26 | |
| 3.1.3 | 1 / 26 | |
| 3.1.2 | 1 / 26 | |
| 3.1.1 | 1 / 26 | |
| 3.1.0 | 1 / 26 | |
| 3.0.1 | 1 / 26 | |
| 3.0.0 | 1 / 26 | |
| 2.0.1 | 7 / 25 | |
| 2.0.0 | 7 / 25 | |
| 1.6.0 | 7 / 25 | |
| 1.5.1 | 7 / 25 | |
| 1.5.0 | 7 / 22 | |
| 1.4.6 | 6 / 22 | |
| 1.4.5 | 5 / 16 | |
| 1.4.4 | 5 / 16 | |
| 1.4.3 | 5 / 16 | |
| 1.4.2 | 5 / 16 | |
| 1.4.1 | 5 / 16 | |
| 1.4.0 | 5 / 16 | |
| 1.3.0 | 5 / 16 | |
| 1.2.1 | 5 / 16 | |
| 1.2.0 | 4 / 16 | |
| 1.1.5 | 3 / 16 | |
| 1.1.4 | 3 / 16 | |
| 1.1.3 | 6 / 16 | |
| 1.1.2 | 5 / 16 | |
| 1.1.1 | 4 / 15 | |
| 1.1.0 | 4 / 13 | |
| 1.0.3 | 3 / 13 | |
| 1.0.2 | 3 / 13 | |
| 1.0.1 | 3 / 13 | |
| 1.0.0 | 3 / 12 |
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-05-26. This could indicate a legitimate maintainer transition or an account compromise.
v3.4.4
2 findingsThis version was published by a different npm account than previous versions on 2020-01-31. 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.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vincentlanglet.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-10-03. This could indicate a legitimate maintainer transition or an account compromise.
v3.4.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vincentlanglet.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-10-02. This could indicate a legitimate maintainer transition or an account compromise.
v3.4.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vincentlanglet.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-08-03. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: adriantoine.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: adriantoine.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: adriantoine.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.