@trezor/transport - npm Package Compare versions

Comparing version 1.0.1-beta.1 to 1.0.1

lib/bridge/v2.js

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

package.json

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

Fixed 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

80415

increased by0.08%

Number of package files

50

increased by2.04%

Number of low quality alerts

1

decreased by-50%

Number of medium supply chain risk alerts

2

decreased by-33.33%

Worsened metrics

Lines of code

2042

decreased by-0.05%

No dependency changes