ospec - npm Package Compare versions

Comparing version 4.1.2 to 4.1.3

package.json

 {
   "name": "ospec",
-  "version": "4.1.2",
+  "version": "4.1.3",
   "description": "Noiseless testing framework",
@@ -13,4 +13,5 @@ "main": "ospec.js",
   "files": [
+    "bin",
     "ospec.js",
-    "bin"
+    "scripts/rename-stable-binaries.js"
   ],
@@ -23,3 +24,3 @@ "bin": "./bin/ospec",
   "scripts": {
-    "postinstall": "node scripts/rename-stable-binaries.js",
+    "postinstall": "node ./scripts/rename-stable-binaries.js",
     "test": "ospec-stable tests/test-*.js",
@@ -37,4 +38,4 @@ "test-api": "ospec-stable tests/test-api.js",
     "eslint": "^6.8.0",
-    "ospec-stable": "npm:ospec@4.1.1-and-then-some"
+    "ospec-stable": "npm:ospec@4.1.2-postinstall-experiments"
   }
 }

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

Deprecated

Maintenance

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Found 1 instance in 1 package

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

Improved metrics

Total package byte prevSize

51975

increased by1.04%

Number of package files

6

increased by20%

Lines of code

697

increased by1.75%

Number of high maintenance alerts

0

decreased by-100%

No dependency changes