@metamask/eth-sig-util - npm Package Compare versions

Comparing version 5.0.0 to 5.0.1

dist/sign-typed-data.js

@@ -92,3 +92,4 @@ "use strict";
         else if ((0, ethjs_util_1.isHexString)(value)) {
-            value = (0, utils_1.numberToBuffer)(parseInt(value, 16));
+            const prepend = value.length % 2 ? '0' : '';
+            value = Buffer.from(prepend + value.slice(2), 'hex');
         }
@@ -95,0 +96,0 @@ else {

package.json

 {
   "name": "@metamask/eth-sig-util",
-  "version": "5.0.0",
+  "version": "5.0.1",
   "description": "A few useful functions for signing ethereum data",
@@ -32,4 +32,3 @@ "keywords": [
     "build:clean": "rimraf dist && yarn build",
-    "docs": "typedoc",
-    "docs:publish": "typedoc --cleanOutputDir false --gitRevision \"v$(jq -r .version < ./package.json)\"",
+    "build:docs": "typedoc",
     "lint": "yarn lint:eslint && yarn lint:misc --check",
@@ -39,4 +38,3 @@ "lint:eslint": "eslint . --cache --ext js,ts",
     "lint:misc": "prettier '**/*.json' '**/*.md' '!CHANGELOG.md' '**/*.yml' '!.yarnrc.yml' --ignore-path .gitignore --no-error-on-unmatched-pattern",
-    "prepublishOnly": "yarn build:clean",
-    "setup": "yarn install",
+    "prepack": "./scripts/prepack.sh",
     "test": "jest",
@@ -43,0 +41,0 @@ "test:watch": "jest --watch"

README.md

@@ -19,3 +19,3 @@ # `@metamask/eth-sig-util`
 
-The full API documentation for the latest published version of this library is [available here](https://metamask.github.io/eth-sig-util/index.html).
+The full API documentation for the latest published version of this library is [available here](https://metamask.github.io/eth-sig-util/latest/index.html).
 
@@ -26,7 +26,6 @@ ## Contributing
 
-- Install [Node.js](https://nodejs.org) version 12
+- Install [Node.js](https://nodejs.org) version 14
   - If you are using [nvm](https://github.com/creationix/nvm#installation) (recommended) running `nvm use` will automatically choose the right node version for you.
-- Install [Yarn v1](https://yarnpkg.com/en/docs/install)
-- Run `yarn setup` to install dependencies and run any requried post-install scripts
-  - **Warning:** Do not use the `yarn` / `yarn install` command directly. Use `yarn setup` instead. The normal install command will skip required post-install scripts, leaving your development environment in an invalid state.
+- Install [Yarn v3](https://yarnpkg.com/getting-started/install)
+- Run `yarn install` to install dependencies and run any required post-install scripts
 
@@ -77,4 +76,4 @@ ### Testing and Linting
 
-   - Be very careful to use a clean local environment to publish the release, and follow exactly the same steps used during CI.
-   - Use `npm publish --dry-run` to examine the release contents to ensure the correct files are included. Compare to previous releases if necessary (e.g. using `https://unpkg.com/browse/[package name]@[package version]/`).
-   - Once you are confident the release contents are correct, publish the release using `npm publish`.
+   - Wait for the `publish-release` GitHub Action workflow to finish. This should trigger a second job (`publish-npm`), which will wait for a run approval by the [`npm publishers`](https://github.com/orgs/MetaMask/teams/npm-publishers) team.
+   - Approve the `publish-npm` job (or ask somebody on the npm publishers team to approve it for you).
+   - Once the `publish-npm` job has finished, check npm to verify that it has been published.

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Deprecated

Maintenance

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Found 1 instance in 1 package

Improved metrics

Lines of code

1607

increased by0.06%

Number of medium maintenance alerts

0

decreased by-100%

Worsened metrics

Total package byte prevSize

143283

decreased by-5.93%

Number of package files

21

decreased by-4.55%

Number of lines in readme file

77

decreased by-1.28%

Number of medium supply chain risk alerts

1

increased byInfinity%

No dependency changes