lockfile-lint - npm Package Compare versions

Comparing version 4.12.0 to 4.12.1

bin/lockfile-lint.js

		@@ -52,3 +52,6 @@ #!/usr/bin/env node

		const lockfilesList = glob.sync(config.path)
		let lockfilesList = []
		if (config.path) {
		lockfilesList = glob.sync(config.path)
		}

		@@ -117,3 +120,3 @@ for (const lockfilePath of lockfilesList) {

		function success(message) {
		function success (message) {
		const m = [
		@@ -125,3 +128,3 @@ isPrettyFormat ? GREEN : '',
		isPrettyFormat ? RESET : ''
		].filter((e) => !!e)
		].filter(e => !!e)

		@@ -131,3 +134,3 @@ console.info(m.join(' '))

		function warn(message) {
		function warn (message) {
		const m = [
		@@ -139,3 +142,3 @@ isPrettyFormat ? YELLOW : '',
		isPrettyFormat ? RESET : ''
		].filter((e) => !!e)
		].filter(e => !!e)

		@@ -145,3 +148,3 @@ console.error(m.join(' '))

		function error(message) {
		function error (message) {
		const m = [
		@@ -153,5 +156,5 @@ isPrettyFormat ? RED : '',
		isPrettyFormat ? RESET : ''
		].filter((e) => !!e)
		].filter(e => !!e)

		console.error(m.join(' '))
		}

package.json

		{
		"name": "lockfile-lint",
		"version": "4.12.0",
		"version": "4.12.1",
		"description": "A CLI to lint a lockfile for security policies",
		@@ -79,3 +79,4 @@ "bin": {
		"open-cli": "^7.2.0",
		"prettier-standard": "16.4.1"
		"prettier-standard": "16.4.1",
		"semver": "^7.5.4"
		},
		@@ -82,0 +83,0 @@ "jest": {

README.md

		@@ -81,3 +81,3 @@ <p align="center"><h1 align="center">
		\|----------------------------------\|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\|---------------\|
		\| `--path`, `-p` \| path to the lockfile but you can also provide a glob matching pattern, for example: `/path/to/dir/**/package-lock.json` to match multiple lockfiles \| ✅ \|
		\| `--path`, `-p` \| path to the lockfile but you can also provide a glob matching pattern as long as it isn't expanded by a shell like bash or zsh. If that's the case, you can provide it as a string, for example: `-p '/Users/lirantal/repos/**/package-lock.json'` to match multiple lockfiles \| ✅ \|
		\| `--type`, `-t` \| lockfile type, options are `npm` or `yarn` \| ✅ \|
		@@ -84,0 +84,0 @@ \| `--format`, `-f` \| sets what type of report output is desired, one of [ `pretty`, `plain` ] with `plain` removing colors & status symbols from output \| ✅ \|

		@@ -81,3 +81,3 @@ <p align="center"><h1 align="center">
		\|----------------------------------\|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\|---------------\|
		\| `--path`, `-p` \| path to the lockfile but you can also provide a glob matching pattern, for example: `/path/to/dir/**/package-lock.json` to match multiple lockfiles \| ✅ \|
		\| `--path`, `-p` \| path to the lockfile but you can also provide a glob matching pattern as long as it isn't expanded by a shell like bash or zsh. If that's the case, you can provide it as a string, for example: `-p '/Users/lirantal/repos/**/package-lock.json'` to match multiple lockfiles \| ✅ \|
		\| `--type`, `-t` \| lockfile type, options are `npm` or `yarn` \| ✅ \|
		@@ -84,0 +84,0 @@ \| `--format`, `-f` \| sets what type of report output is desired, one of [ `pretty`, `plain` ] with `plain` removing colors & status symbols from output \| ✅ \|

New alerts