@loopback/core - npm Package Compare versions

Comparing version 0.2.4 to 0.3.0

CHANGELOG.md

@@ -6,2 +6,10 @@ # Change Log
 
+<a name="0.3.0"></a>
+# [0.3.0](https://github.com/strongloop/loopback-next/compare/@loopback/core@0.2.4...@loopback/core@0.3.0) (2018-03-21)
+
+
+
+
+**Note:** Version bump only for package @loopback/core
+
 <a name="0.2.4"></a>
@@ -8,0 +16,0 @@ ## [0.2.4](https://github.com/strongloop/loopback-next/compare/@loopback/core@0.2.3...@loopback/core@0.2.4) (2018-03-14)

package.json

 {
   "name": "@loopback/core",
-  "version": "0.2.4",
+  "version": "0.3.0",
   "description": "",
@@ -24,7 +24,7 @@ "engines": {
   "dependencies": {
-    "@loopback/context": "^0.2.4"
+    "@loopback/context": "^0.3.0"
   },
   "devDependencies": {
     "@loopback/build": "^0.3.2",
-    "@loopback/testlab": "^0.3.3"
+    "@loopback/testlab": "^0.4.0"
   },
@@ -31,0 +31,0 @@ "files": [

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

496923

increased by0.04%

Worsened metrics

Number of medium supply chain risk alerts

5

increased by25%

Dependency changes

• + Added@loopback/context@0.3.0(transitive)

• + Added@loopback/metadata@0.3.1(transitive)

• - Removed@loopback/context@0.2.4(transitive)

• - Removed@loopback/metadata@0.2.4(transitive)

• Updated@loopback/context@^0.3.0