npm-registry - npm Package Compare versions

Comparing version 0.1.1 to 0.1.2

normalize/packages.js

@@ -27,3 +27,6 @@ 'use strict';
     return semver.gt(a, b) ? -1 : 1;
-  });
+  }).reduce(function reduce(result, release) {
+    result[release] = data.versions[release]._npmUser;
+    return result;
+  }, {});
 
@@ -30,0 +33,0 @@ //

package.json

 {
   "name": "npm-registry",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "An high available npm registry client",
@@ -5,0 +5,0 @@ "main": "index.js",

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

Improved metrics

Total package byte prevSize

30617

increased by0.41%

Lines of code

798

increased by0.38%

Worsened metrics

Number of medium supply chain risk alerts

1

increased byInfinity%

No dependency changes