ospec - npm Package Compare versions

Comparing version 3.1.0 to 4.0.0

change-log.md

@@ -15,2 +15,5 @@ # Change log for ospec
 
+### 4.0.0
+- Pull ESM support out
+
 ### 3.1.0
@@ -17,0 +20,0 @@ - ospec: Test results now include `.message` and `.context` regardless of whether the test passed or failed. (#2227 @robertakarobin)

package.json

 {
   "name": "ospec",
-  "version": "3.1.0",
+  "version": "4.0.0",
   "description": "Noiseless testing framework",
   "main": "ospec.js",
-  "module": "ospec.mjs",
   "directories": {
@@ -16,5 +15,2 @@ "test": "tests"
   },
-  "scripts": {
-    "prepublishOnly": "node esm.js"
-  },
   "repository": "MithrilJS/mithril.js",
@@ -21,0 +17,0 @@ "dependencies": {

README.md

@@ -1,2 +0,2 @@
-ospec [![NPM Version](https://img.shields.io/npm/v/ospec.svg)](https://www.npmjs.com/package/ospec) [![NPM License](https://img.shields.io/npm/l/ospec.svg)](https://www.npmjs.com/package/ospec)
+ospec [![npm Version](https://img.shields.io/npm/v/ospec.svg)](https://www.npmjs.com/package/ospec) [![npm License](https://img.shields.io/npm/l/ospec.svg)](https://www.npmjs.com/package/ospec)
 =====
@@ -374,3 +374,3 @@
 
-ospec comes with an executable named `ospec`. NPM auto-installs local binaries to `./node_modules/.bin/`. You can run ospec by running `./node_modules/.bin/ospec` from your project root, but there are more convenient methods to do so that we will soon describe.
+ospec comes with an executable named `ospec`. npm auto-installs local binaries to `./node_modules/.bin/`. You can run ospec by running `./node_modules/.bin/ospec` from your project root, but there are more convenient methods to do so that we will soon describe.
 
@@ -377,0 +377,0 @@ ospec doesn't work when installed globally (`npm install -g`). Using global scripts is generally a bad idea since you can end up with different, incompatible versions of the same package installed locally and globally.

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

Filesystem access

Supply chain risk

Accesses the file system, and could potentially read sensitive data.

Found 1 instance in 1 package

Improved metrics

Number of low supply chain risk alerts

1

decreased by-50%

Number of medium supply chain risk alerts

4

decreased by-20%

Worsened metrics

Total package byte prevSize

59011

decreased by-19.31%

Number of package files

9

decreased by-18.18%

Lines of code

1033

decreased by-27%

No dependency changes