Installations

npm install is-ci

Score

99.7

Supply Chain

69.4

Quality

78.3

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

0

Total

15

Closed

3

Merged

12

Issues

Open

1

Total

10

Closed

9

Releases

1

v3.0.1

Published on 26 Oct 2021

View all 1 releases

Developer

watson

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

No

Node Version

16.12.0

NPM Version

8.1.0 Statistics

385 Stars

82 Commits

17 Forks

7 Watching

1 Branches

11 Contributors

Updated on 27 Nov 2024

Bundle Size

5.03 kB

Minified

1.79 kB

Minified + Gzipped

Bundlephobia

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

5,425,431,405

Last day

-9.4%

4,023,133

Compared to previous day

Last week

1.9%

24,553,450

Compared to previous week

Last month

21.8%

96,538,033

Compared to previous month

Last year

-11.5%

974,377,107

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

1

ci-info

Dev Dependencies

2

clear-module standard

Versions

is-ci

Returns true if the current environment is a Continuous Integration server.

Please open an issue if your CI server isn't properly detected :)

Installation

1npm install is-ci --save

Programmatic Usage

1const isCI = require('is-ci')
2
3if (isCI) {
4  console.log('The code is running on a CI server')
5}

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

1is-ci && echo "This is a CI server"

Supported CI tools

Refer to ci-info docs for all supported CI's

License

MIT

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

License

Determines if the project has defined a license.

1

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

Score

3.5

/10

Last Scanned on 2024-11-18

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More