supports-hyperlinks
npmv4.5.0TypeScriptDetect whether a terminal supports hyperlinks
Safe to adopt
Yes — supports-hyperlinks scores well across adoption, maintenance, weight, supply chain, and licensing. 35.4M downloads per week and 1 known dependents. Last published 82 days ago. 8 releases in the last 2 years.
- AAdoption: grade A, Excellent.
35.4M downloads per week and 1 known dependents.
- AMaintenance: grade A, Excellent.
Last published 82 days ago. 8 releases in the last 2 years.
- AWeight: grade A, Excellent.
Pulls in 2 transitive packages, about 13 KB installed (at least — some of the tree is still being crawled).
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding supports-hyperlinks to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.
Licenses in the dependency tree
Every license you inherit by installing supports-hyperlinks, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >=20
- Module format
- ESM only
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the supports-hyperlinks README.
import supportsHyperlinks from 'supports-hyperlinks';
if (supportsHyperlinks.stdout) {
console.log('Terminal stdout supports hyperlinks');
}
if (supportsHyperlinks.stderr) {
console.log('Terminal stderr supports hyperlinks');
}supports-hyperlinks vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| supports-hyperlinksthis page | 35.4M | 1 | MIT | 2 months ago |
| terminal-link | 18.8M | 1 | MIT | 1 day ago |
| is-wsl | 117.6M | 4 | MIT | 1 day ago |
| string-width | 0 | 3 | MIT | 1 day ago |
| has-flag | 166.9M | 1 | MIT | 1 day ago |
| picocolors | 0 | 16 | ISC | 1 day ago |
Dependencies
Declared by supports-hyperlinks v4.5.0. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (2)
Dev (4)
Used by
Popular packages that depend on supports-hyperlinks.
Relationship graph
Dependencies (left) and dependents (right) of supports-hyperlinks.
Release history
8 releases in the last two years, typically about 165 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 4.5.0latest | 2 months ago | 8.3 KB | MIT |
| 4.4.0 | 8 months ago | 7.8 KB | MIT |
| 4.3.0 | 11 months ago | 7.8 KB | MIT |
| 4.2.0 | 11 months ago | 7.4 KB | MIT |
| 4.1.2 | 1 year ago | 7.4 KB | MIT |
| 4.1.0 | 1 year ago | 7.4 KB | MIT |
| 4.0.0 | 1 year ago | 7.2 KB | MIT |
| 3.2.0 | 1 year ago | 6.8 KB | MIT |
| 3.1.0 | 2 years ago | 7.3 KB | MIT |
| 3.0.0 | 3 years ago | 7.3 KB | MIT |
| 2.3.0 | 4 years ago | 6.8 KB | MIT |
| 2.2.0 | 5 years ago | 6.5 KB | MIT |
| 2.1.0 | 6 years ago | 6.5 KB | MIT |
| 2.0.0 | 7 years ago | 6.3 KB | MIT |
| 1.0.1 | 8 years ago | — | MIT |
Overview
supports-hyperlinks is an npm package that detect whether a terminal supports hyperlinks. It is extremely widely used, with about 35.4M downloads per week and 1 known dependents in the graph. The latest version is 4.5.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need detect whether a terminal supports hyperlinks and value a battle-tested, widely-adopted solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.
Pros
- Large, well-established user base (35.4M weekly downloads).
- Ships TypeScript type definitions.
- Clear open-source license (MIT).
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Funding
Frequently asked questions
Should I use supports-hyperlinks?
Yes — supports-hyperlinks scores well across adoption, maintenance, weight, supply chain, and licensing. 35.4M downloads per week and 1 known dependents. Last published 82 days ago. 8 releases in the last 2 years.
How do I install supports-hyperlinks?
Run `npm install supports-hyperlinks` to add supports-hyperlinks to your npm project.
How many dependencies does supports-hyperlinks have?
supports-hyperlinks declares 6 direct dependencies and pulls in 2 packages in total once its runtime tree is resolved totalling about 13 KB on disk.
What license is supports-hyperlinks released under?
supports-hyperlinks is distributed under the MIT license.
How popular is supports-hyperlinks?
supports-hyperlinks has approximately 35,387,203 downloads per week and 1 known dependent packages.
Is supports-hyperlinks still maintained?
The most recent release of supports-hyperlinks (v4.5.0) was published 2 months ago.
Does supports-hyperlinks run install scripts?
No. supports-hyperlinks does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.