history - npm Package Compare versions

Comparing version 1.9.0 to 1.9.1

package.json

 {
   "name": "history",
-  "version": "1.9.0",
+  "version": "1.9.1",
   "description": "A minimal, functional history implementation for JavaScript",
@@ -17,2 +17,4 @@ "main": "lib/index",
     "test": "eslint modules && karma start",
+    "lint": "eslint modules",
+    "postinstall": "node -e \"require('fs').stat('lib', function (e, s) { process.exit(e || !s.isDirectory() ? 1 : 0) })\" || npm run build",
     "prepublish": "npm run build"
@@ -31,2 +33,3 @@ },
   "devDependencies": {
+    "assert": "1.3.0",
     "babel": "^5.4.7",
@@ -36,4 +39,5 @@ "babel-core": "^5.4.7",
     "babel-loader": "^5.0.0",
-    "eslint": "^1.0.0",
-    "expect": "^1.8.0",
+    "eslint": "1.4.1",
+    "eslint-plugin-react": "3.3.2",
+    "expect": "1.10.0",
     "karma": "^0.13.3",
@@ -40,0 +44,0 @@ "karma-browserstack-launcher": "^0.1.3",

New alerts

Install scripts

Supply chain risk

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Found 1 instance in 1 package

Fixed alerts

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

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

Improved metrics

Total package byte prevSize

160759

increased by18.51%

Number of package files

45

increased by55.17%

Lines of code

3350

increased by33.89%

Number of medium supply chain risk alerts

0

decreased by-100%

Worsened metrics

Dev dependency count

20

increased by11.11%

Number of high supply chain risk alerts

1

increased byInfinity%

No dependency changes