Gathering detailed insights and metrics for is-interactive
Gathering detailed insights and metrics for is-interactive
Installations
npm install is-interactiveScore
99.3
Supply Chain
76.6
Quality
75.2
Maintenance
100
Vulnerability
100
License
Developer
sindresorhus
Developer Guide
BETA
Module System
ESM
Min. Node Version
>=12
Typescript Support
No
Node Version
16.0.0
NPM Version
7.10.0
Statistics
115 Stars
10 Commits
5 Forks
3 Watching
1 Branches
3 Contributors
Updated on 30 Jul 2024
Languages
JavaScript (84.75%)
TypeScript (15.25%)
Total Downloads
Cumulative downloads
Total Downloads
2,446,324,290
Last day
-7.3%
4,156,832
Compared to previous day
Last week
2.2%
23,971,897
Compared to previous week
Last month
7.6%
100,091,477
Compared to previous month
Last year
39.1%
1,019,136,852
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dev Dependencies
4
Versions
is-interactive
Check if stdout or stderr is interactive
It checks that the stream is TTY, not a dumb terminal, and not running in a CI.
This can be useful to decide whether to present interactive UI or animations in the terminal.
Install
1npm install is-interactive
Usage
1import isInteractive from 'is-interactive'; 2 3isInteractive(); 4//=> true
API
isInteractive(options?)
options
Type: object
stream
Type: stream.Writable
Default: process.stdout
The stream to check.
FAQ
Why are you not using ci-info for the CI check?
It's silly to have to detect individual CIs. They should identify themselves with the CI environment variable, and most do just that. A manually maintained list of detections will easily get out of date. And if a package using ci-info doesn't update to the latest version all the time, they will not support certain CIs. It also creates unpredictability as you might assume a CI is not supported and then suddenly it gets supported and you didn't account for that. In addition, some of the manual detections are loose and might cause false-positives which could create hard-to-debug bugs.
Why does this even exist? It's just a few lines.
It's not about the number of lines, but rather discoverability and documentation. A lot of people wouldn't even know they need this. Feel free to copy-paste the code if you don't want the dependency. You might also want to read this blog post.
Related
- is-in-ci - Check if the process is running in a Continuous Integration (CI) environment
- is-unicode-supported - Detect whether the terminal supports Unicode
- supports-color - Detect whether a terminal supports color
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
security policy file detected
Details
- Info: security policy file detected: .github/security.md:1
- Info: Found linked content: .github/security.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: .github/security.md:1
- Info: Found text in security policy: .github/security.md:1
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
- Info: project has a license file: license:0
- Info: FSF or OSI recognized license: MIT License: license:0
Reason
Found 2/10 approved changesets -- score normalized to 2
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/sindresorhus/is-interactive/main.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/sindresorhus/is-interactive/main.yml/main?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/main.yml:22
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 npmCommand dependencies pinned
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/main.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'main'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 2 are checked with a SAST tool
Score
4.2
/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