fixpack - npm Package Compare versions

Comparing version 2.3.0 to 2.3.1

fixpack.js

 #!/usr/bin/env node
+var ALCE = require('alce')
+var extend = require('extend-object')
 var fs = require('fs')
 var path = require('path')
-var ALCE = require('alce')
-var defaultConfig = require('./config')
-var extend = require('extend-object')
 require('colors')
 
+var defaultConfig = require('./config')
+
 function checkMissing (pack, config) {
@@ -70,2 +71,6 @@ var warnItems
 
+  // sometimes people use a string rather than an array for the `keywords`
+  // field when there is only one item listed
+  if (typeof out.keywords === 'string') out.keywords = [out.keywords]
+
   // sort some sub items alphabetically
@@ -72,0 +77,0 @@ config.sortedSubItems.forEach(function (key) {

package.json

 {
   "name": "fixpack",
   "description": "cli tool that cleans up package.json files.",
-  "version": "2.3.0",
+  "version": "2.3.1",
   "author": "Henrik Joreteg <[e-mail]>",
@@ -6,0 +6,0 @@ "bin": "./bin/fixpack",

New 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

Improved metrics

Total package byte prevSize

7622

increased by4.41%

Lines of code

132

increased by36.08%

Worsened metrics

Number of medium supply chain risk alerts

1

increased byInfinity%

No dependency changes