openapi-enforcer - npm Package Compare versions

Comparing version 0.0.1 to 0.0.2

package.json

 {
   "name": "openapi-enforcer",
-  "version": "0.0.1",
-  "description": "Validate openapi schemas against values, connect middleware, request parsing and validating, response formatting and validating, and response building tools.",
+  "version": "0.0.2",
+  "description": "Automatically validate a value against the swagger schema while you build it. Alternatively you can validate the final value.",
   "main": "index.js",
+  "directories": {
+    "test": "tests"
+  },
   "scripts": {
-    "test": "echo \"Error: no test specified\" && exit 1"
+    "test": "mocha test/*.js",
+    "coverage": "nyc --reporter=html mocha test/*.js",
+    "coverage:report": "nyc mocha test/*.js && nyc report --reporter=text-lcov | coveralls"
   },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/byu-oit/swagger-enforcer.git"
+  },
   "keywords": [
-    "openapi",
     "swagger",
-    "validate",
-    "error",
-    "schema",
-    "request",
     "response",
-    "connect",
-    "middleware"
+    "build",
+    "compose",
+    "validate"
   ],
-  "author": "James Speirs <[e-mail]>",
-  "license": "Apache-2.0"
+  "author": "James Speirs",
+  "license": "Apache-2.0",
+  "bugs": {
+    "url": "https://github.com/byu-oit/swagger-enforcer/issues"
+  },
+  "homepage": "https://github.com/byu-oit/swagger-enforcer#readme",
+  "devDependencies": {
+    "body-parser": "^1.18.2",
+    "chai": "^3.5.0",
+    "connect-busboy": "0.0.2",
+    "connect-multiparty": "^2.1.0",
+    "coveralls": "^2.13.0",
+    "express": "^4.16.2",
+    "formidable": "^1.1.1",
+    "js-yaml": "^3.10.0",
+    "json-schema-ref-parser": "^4.0.4",
+    "mocha": "^2.4.5",
+    "multer": "^1.3.0",
+    "multiparty": "^4.1.3",
+    "nyc": "^10.2.0",
+    "request": "^2.83.0",
+    "request-promise-native": "^1.0.5",
+    "swagger-parser": "^3.4.2"
+  },
+  "dependencies": {}
 }

New 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

Dynamic require

Supply chain risk

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

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

Fixed alerts

Empty package

Supply chain risk

Package does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish.

Found 1 instance in 1 package

No README

Quality

Package does not have a README. This may indicate a failed publish or a low quality package.

Found 1 instance in 1 package

No bug tracker

Maintenance

Package does not have a linked bug tracker in package.json.

Found 1 instance in 1 package

No repository

Supply chain risk

Package does not have a linked source code repository. Without this field, a package will have no reference to the location of the source code use to generate the package.

Found 1 instance in 1 package

No tests

Quality

Package does not have any tests. This is a strong signal of a poorly maintained or low quality package.

Found 1 instance in 1 package

No website

Quality

Package does not have a website.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

268849

increased by47066.49%

Number of package files

28

increased by2700%

Lines of code

3946

increased byInfinity%

Number of low maintenance alerts

0

decreased by-100%

Number of low quality alerts

1

decreased by-66.67%

Number of medium quality alerts

0

decreased by-100%

Number of lines in readme file

462

increased byInfinity%

Worsened metrics

Dev dependency count

16

increased byInfinity%

Number of low supply chain risk alerts

2

increased by100%

No dependency changes