schema-utils - npm Package Compare versions

Comparing version 0.1.0 to 0.2.1

CHANGELOG.md

@@ -5,2 +5,16 @@ # Change Log
 
+<a name="0.2.1"></a>
+## [0.2.1](https://github.com/webpack-contrib/schema-utils/compare/v0.2.0...v0.2.1) (2017-03-13)
+
+
+### Bug Fixes
+
+* Include .babelrc to `files` ([28f0363](https://github.com/webpack-contrib/schema-utils/commit/28f0363))
+* Include source to `files` ([43b0f2f](https://github.com/webpack-contrib/schema-utils/commit/43b0f2f))
+
+
+
+<a name="0.2.0"></a>
+# [0.2.0](https://github.com/webpack-contrib/schema-utils/compare/v0.1.0...v0.2.0) (2017-03-12)
+
 <a name="0.1.0"></a>
@@ -7,0 +21,0 @@ # 0.1.0 (2017-03-07)

dist/index.js

 Object.defineProperty(exports, "__esModule", {
   value: true
 });
+exports.validateOptions = undefined;
 
 var _validateOptions = require('./lib/validate-options');
 
-exports.default = _validateOptions.validateOptions;
+var _validateOptions2 = _interopRequireDefault(_validateOptions);
+
+function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { default: obj }; }
+
+exports.validateOptions = _validateOptions2.default;
 //# sourceMappingURL=index.js.map

package.json

 {
   "name": "schema-utils",
-  "version": "0.1.0",
+  "version": "0.2.1",
   "description": "Webpack Schema Validation Utilities",
   "main": "dist/index.js",
   "files": [
-    "dist"
+    "dist",
+    "lib",
+    "src",
+    ".babelrc"
   ],
@@ -24,2 +27,3 @@ "scripts": {
     "lint-staged": "lint-staged",
+    "postinstall": "node lib/post_install.js",
     "prepublish": "yarn run build",
@@ -26,0 +30,0 @@ "release": "yarn run standard-version"

README.md

@@ -31,3 +31,18 @@ [![npm][npm]][npm-url]
 
+```javascript
+const { validateSchema } = require('schema-utils');
 
+...
+
+// This injects possible default values to options
+const validation = validateSchema(jsonSchema, options);
+
+if(validation.isValid) {
+  throw new Error(validation.error);
+}
+
+// options are ok to use now
+```
+
+
 <h2 align="center">Maintainers</h2>
@@ -34,0 +49,0 @@

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

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

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

Shell access

Supply chain risk

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Found 1 instance in 1 package

Environment variable access

Supply chain risk

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

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

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

Improved metrics

Total package byte prevSize

13314

increased by64.8%

Number of package files

13

increased by62.5%

Lines of code

180

increased by650%

Number of lines in readme file

84

increased by21.74%

Worsened metrics

Number of high supply chain risk alerts

1

increased byInfinity%

Number of low supply chain risk alerts

2

increased byInfinity%

Number of medium supply chain risk alerts

2

increased byInfinity%

No dependency changes