Gathering detailed insights and metrics for supports-hyperlinks
Gathering detailed insights and metrics for supports-hyperlinks
Detect whether a terminal emulator supports hyperlinks
Installations
npm install supports-hyperlinksScore
98.2
Supply Chain
80.1
Quality
80.2
Maintenance
100
Vulnerability
100
License
Releases
6
Contributors
8
Developer
jamestalmage
Developer Guide
BETA
Module System
ESM, UMD
Min. Node Version
>=14.18
Typescript Support
Yes
Node Version
18.20.4
NPM Version
10.6.0
Statistics
54 Stars
32 Commits
13 Forks
5 Watching
1 Branches
8 Contributors
Updated on 20 Aug 2024
Languages
JavaScript (100%)
Total Downloads
Cumulative downloads
Total Downloads
3,215,687,730
Last day
-26.7%
2,850,462
Compared to previous day
Last week
-6%
20,523,768
Compared to previous week
Last month
16.7%
84,591,790
Compared to previous month
Last year
-0.9%
835,361,772
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
2
Dev Dependencies
7
Versions
supports-hyperlinks 
Detect whether a terminal emulator supports hyperlinks
Terminal emulators are starting to support hyperlinks. While many terminals have long detected URL's and linkified them, allowing you to Command-Click or Control-Click them to open a browser, you were forced to print the long unsightly URL's on the screen. As of spring 2017 a few terminals began supporting HTML like links, where the link text and destination could be specified separately.
This module allows you to detect if hyperlinks are supported in the current Terminal.
As this is a new development, we anticipate the list of supported Terminals to grow rapidly. Please open an issue or submit a PR as new Terminals implement support.
Install
1npm install supports-hyperlinks
Usage
1const supportsHyperlinks = require('supports-hyperlinks'); 2 3if (supportsHyperlinks.stdout) { 4 console.log('Terminal stdout supports hyperlinks'); 5} 6 7if (supportsHyperlinks.stderr) { 8 console.log('Terminal stderr supports hyperlinks'); 9}
API
Returns an Object with a stdout and stderr property for testing either streams. Each property is a boolean, indicating whether or not hyperlinks are supported.
Info
Obeys the --no-hyperlinks, --hyperlink=always, and --hyperlink=never CLI flags.
Can be overridden by the user with the flags --hyperlinks=always and --no-hyperlinks. For situations where using those flags are not possible, add the environment variable FORCE_HYPERLINK=1 to forcefully enable hyperlinks or FORCE_HYPERLINK=0 to forcefully disable. The use of FORCE_HYPERLINK overrides all other hyperlink support checks.
Related
hyperlinker: Write hyperlinks for the Terminal.
License
MIT © James Talmage
No vulnerabilities found.
Reason
GitHub workflow tokens follow principle of least privilege
Details
- Info: topLevel 'contents' permission set to 'read': .github/workflows/node.yml:14
- Info: no jobLevel write permissions found
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
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 8/25 approved changesets -- score normalized to 3
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/node.yml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/jamestalmage/supports-hyperlinks/node.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/jamestalmage/supports-hyperlinks/node.yml/master?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/node.yml:35
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 npmCommand dependencies pinned
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
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 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 14 are checked with a SAST tool
Score
4.7
/10
Last Scanned on 2024-11-25
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