is-ci - npm Package Compare versions

Comparing version 1.0.10 to 1.1.0

package.json

 {
   "name": "is-ci",
-  "version": "1.0.10",
+  "version": "1.1.0",
   "description": "Detect if your code is running on a CI server",
+  "bin": "bin.js",
   "main": "index.js",
@@ -11,3 +12,3 @@ "dependencies": {
     "clear-require": "^1.0.1",
-    "standard": "^5.3.1"
+    "standard": "^10.0.3"
   },
@@ -35,5 +36,5 @@ "scripts": {
   "coordinates": [
-    55.6876732,
-    12.5955341
+    56.0093252,
+    11.9592058
   ]
 }

README.md

@@ -18,6 +18,6 @@ # is-ci
 
-## Usage
+## Programmatic Usage
 
 ```js
-var isCI = require('is-ci')
+const isCI = require('is-ci')
 
@@ -29,2 +29,17 @@ if (isCI) {
 
+## CLI Usage
+
+For CLI usage you need to have the `is-ci` executable in your `PATH`.
+There's a few ways to do that:
+
+- Either install the module globally using `npm install is-ci -g`
+- Or add the module as a dependency to your app in which case it can be
+  used inside your package.json scripts as is
+- Or provide the full path to the executable, e.g.
+  `./node_modules/.bin/is-ci`
+
+```
+is-ci && echo "This is a CI server"
+```
+
 ## Supported CI tools
@@ -31,0 +46,0 @@

test.js

@@ -6,3 +6,3 @@ 'use strict'
 
-if (!process.env.TRAVIS) process.env.CI = 'true'
+process.env.CI = 'true'
 
@@ -14,2 +14,4 @@ var isCI = require('./')
 delete process.env.CONTINUOUS_INTEGRATION
+delete process.env.BUILD_NUMBER
+delete process.env.TRAVIS
 
@@ -16,0 +18,0 @@ clearRequire('./')

New alerts

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

Improved metrics

Total package byte prevSize

4408

increased by14.43%

Lines of code

19

increased by35.71%

Number of lines in readme file

70

increased by27.27%

Worsened metrics

Number of low supply chain risk alerts

5

increased by25%

No dependency changes