Comparing version 0.3.1 to 1.0.0
{ | ||
"name": "read-yaml", | ||
"description": "Very thin wrapper around js-yaml for directly reading in YAML files.", | ||
"version": "0.3.1", | ||
"version": "1.0.0", | ||
"homepage": "https://github.com/jonschlinkert/read-yaml", | ||
@@ -6,0 +6,0 @@ "author": { |
@@ -62,2 +62,2 @@ # read-yaml [![NPM version](https://badge.fury.io/js/read-yaml.svg)](http://badge.fury.io/js/read-yaml) [![Build Status](https://travis-ci.org/jonschlinkert/read-yaml.svg)](https://travis-ci.org/jonschlinkert/read-yaml) | ||
[js-yaml]: https://github.com/nodeca/js-yaml | ||
[js-yaml]: https://github.com/nodeca/js-yaml |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis 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 riskA 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
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
5612
0
63
0