@metamask/eth-sig-util versions and release history
Inspect a published release before upgrading or adding a dependency. Each version reference keeps its metadata and provider measurements pinned to that exact npm version.
| Published versions | 20 |
|---|---|
| Stable versions | 20 |
| Prereleases | 0 |
| Releases published in the last 90 days | 1 |
| Deprecated releases | 4 |
| Latest npm dist-tag | 9.0.0 |
All available releases
| Version | Published | Runtime dependencies | Types | Status |
|---|---|---|---|---|
| 9.0.0 | 2026-08-26T12:49:49.460Z | 7 | Not declared | latest |
| 8.2.0 | 2025-01-28T20:55:34.015Z | 7 | Bundled | |
| 8.1.2 | 2024-12-17T20:14:34.484Z | 6 | Bundled | |
| 8.1.1 | 2024-12-06T16:23:26.999Z | 6 | Bundled | |
| 8.1.0 | 2024-12-03T14:59:48.256Z | 6 | Bundled | Deprecated due to signTypedData bug affecting Permit signatures |
| 8.0.0 | 2024-10-18T11:23:14.574Z | 6 | Bundled | |
| 7.0.3 | 2024-07-16T00:23:23.365Z | 6 | Bundled | |
| 7.0.2 | 2024-05-01T07:19:56.885Z | 6 | Bundled | |
| 7.0.1 | 2023-11-22T00:06:15.484Z | 6 | Bundled | |
| 6.0.2 | 2023-11-21T22:53:38.219Z | 7 | Bundled | |
| 7.0.0 | 2023-09-12T21:25:30.526Z | 7 | Bundled | This version generates invalid signatures for messages that include the value "0x" in a "bytes" field. This has been fixed in v6.0.2 and v7.0.1 |
| 6.0.1 | 2023-09-11T13:19:50.884Z | 7 | Bundled | This version generates invalid signatures for messages that include the value "0x" in a "bytes" field. This has been fixed in v6.0.2 and v7.0.1 |
| 6.0.0 | 2023-06-30T10:57:29.962Z | 6 | Bundled | |
| 5.1.0 | 2023-05-01T12:06:02.676Z | 6 | Bundled | |
| 5.0.3 | 2023-04-27T12:47:37.654Z | 6 | Bundled | |
| 5.0.2 | 2022-11-10T21:56:15.449Z | 6 | Bundled | |
| 5.0.1 | 2022-11-09T22:43:57.717Z | 6 | Bundled | |
| 5.0.0 | 2022-09-15T17:44:36.564Z | 6 | Not declared | Deprecated due to eth_signTypedData signing bug; use v5.0.1 instead |
| 4.0.1 | 2022-04-21T21:42:17.272Z | 5 | Not declared | |
| 4.0.0 | 2021-09-22T12:27:28.380Z | 5 | Not declared |
Choosing a version
The latest tag is selected by the publisher and is not a guarantee of compatibility. Prerelease and deprecated status remain visible. Check your Node.js range and peer requirements on the exact version page, then review the maintainer’s release notes before upgrading.
Removed or unpublished versions may be absent. Historical download charts cover all package versions and do not show adoption of an individual release.
npm release-history source — retrieved 2026-10-30T02:34:54.716Z