@trezor/transport - npm Package Compare versions

Comparing version 1.0.0 to 1.0.1-beta.1

lib/bridge/v2.js

@@ -114,2 +114,3 @@ "use strict";
         return __awaiter(this, void 0, void 0, function* () {
+            console.log('call data', JSON.stringify(data, null, 2));
             if (this._messages == null) {
@@ -116,0 +117,0 @@ throw new Error(`Transport not configured.`);

lib/index.js

@@ -7,2 +7,6 @@ "use strict";
 const webusb_1 = require("./lowlevel/webusb");
+const protobuf = require("protobufjs/light");
+const Long = require("long");
+protobuf.util.Long = Long;
+protobuf.configure();
 exports.default = {
@@ -9,0 +13,0 @@ BridgeV2: v2_1.default,

package.json

 {
   "name": "@trezor/transport",
-  "version": "1.0.0",
+  "version": "1.0.1-beta.1",
   "description": "Low level library facilitating protocol buffers based communication with Trezor devices",
@@ -5,0 +5,0 @@ "license": "SEE LICENSE IN LICENSE.md",

New alerts

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

No v1

Quality

Package is not semver >=1. This means it is not stable and does not support ^ ranges.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

80348

increased by0.25%

Lines of code

2043

increased by0.25%

Worsened metrics

Number of low quality alerts

2

increased by100%

Number of medium supply chain risk alerts

3

increased by50%

No dependency changes