can-map-define - npm Package Compare versions

Comparing version 3.0.0-pre.5 to 3.0.0

package.json

 {
   "name": "can-map-define",
-  "version": "3.0.0-pre.5",
+  "version": "3.0.0",
   "description": "Define rich attribute behavior",
@@ -39,6 +39,6 @@ "homepage": "https://canjs.com",
   "dependencies": {
-    "can-compute": "^3.0.0-pre.2",
-    "can-event": "^3.0.0-pre.2",
-    "can-map": "^3.0.0-pre.11",
-    "can-util": "^3.0.0-pre.10",
+    "can-compute": "^3.0.0",
+    "can-event": "^3.0.1",
+    "can-map": "^3.0.1",
+    "can-util": "^3.0.1",
     "jquery": "~2.2.1"
@@ -45,0 +45,0 @@ },

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

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

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

Number of low quality alerts

0

decreased by-100%

Number of medium supply chain risk alerts

0

decreased by-100%

Worsened metrics

Total package byte prevSize

79251

decreased by-17.04%

Number of package files

25

decreased by-19.35%

Dependency changes

• Updatedcan-compute@^3.0.0

• Updatedcan-event@^3.0.1

• Updatedcan-map@^3.0.1

• Updatedcan-util@^3.0.1