Gathering detailed insights and metrics for ansi-regex
Gathering detailed insights and metrics for ansi-regex
Regular expression for matching ANSI escape codes
Installations
npm install ansi-regexDeveloper Guide
BETA
Typescript
Yes
Module System
ESM
Min. Node Version
>=12
Node Version
18.20.4
NPM Version
10.6.0
Score
99.7
Supply Chain
81.3
Quality
79
Maintenance
100
Vulnerability
100
License
Releases
6
Languages
2
JavaScript
TypeScript
JavaScript (99.04%)
TypeScript (0.96%)
Developer
chalk
Download Statistics
Total Downloads
35,608,864,109
Last Day
14,357,073
Last Week
222,979,334
Last Month
954,964,286
Last Year
9,297,874,923
GitHub Statistics
MIT License
195 Stars
57 Commits
80 Forks
16 Watchers
4 Branches
12 Contributors
Updated on Jun 27, 2025
Bundle Size
502.00 B
Minified
346.00 B
Minified + Gzipped
Sponsor this package
Maintainers
2
Package Meta Information
Latest Version
6.1.0
Package Id
ansi-regex@6.1.0
Unpacked Size
5.29 kB
Size
2.60 kB
File Count
5
NPM Version
10.6.0
Node Version
18.20.4
Published on
Sep 09, 2024
Total Downloads
Cumulative downloads
Total Downloads
35,608,864,109
Last Day
-2.2%
14,357,073
Compared to previous day
Last Week
-6.2%
222,979,334
Compared to previous week
Last Month
3.7%
954,964,286
Compared to previous month
Last Year
27.6%
9,297,874,923
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dev Dependencies
4
ansi-regex
Regular expression for matching ANSI escape codes
Install
1npm install ansi-regex
Usage
1import ansiRegex from 'ansi-regex'; 2 3ansiRegex().test('\u001B[4mcake\u001B[0m'); 4//=> true 5 6ansiRegex().test('cake'); 7//=> false 8 9'\u001B[4mcake\u001B[0m'.match(ansiRegex()); 10//=> ['\u001B[4m', '\u001B[0m'] 11 12'\u001B[4mcake\u001B[0m'.match(ansiRegex({onlyFirst: true})); 13//=> ['\u001B[4m'] 14 15'\u001B]8;;https://github.com\u0007click\u001B]8;;\u0007'.match(ansiRegex()); 16//=> ['\u001B]8;;https://github.com\u0007', '\u001B]8;;\u0007']
API
ansiRegex(options?)
Returns a regex for matching ANSI escape codes.
options
Type: object
onlyFirst
Type: boolean
Default: false (Matches any ANSI escape codes in a string)
Match only the first ANSI escape.
FAQ
Why do you test for codes not in the ECMA 48 standard?
Some of the codes we run as a test are codes that we acquired finding various lists of non-standard or manufacturer specific codes. We test for both standard and non-standard codes, as most of them follow the same or similar format and can be safely matched in strings without the risk of removing actual string content. There are a few non-standard control codes that do not follow the traditional format (i.e. they end in numbers) thus forcing us to exclude them from the test because we cannot reliably match them.
On the historical side, those ECMA standards were established in the early 90's whereas the VT100, for example, was designed in the mid/late 70's. At that point in time, control codes were still pretty ungoverned and engineers used them for a multitude of things, namely to activate hardware ports that may have been proprietary. Somewhere else you see a similar 'anarchy' of codes is in the x86 architecture for processors; there are a ton of "interrupts" that can mean different things on certain brands of processors, most of which have been phased out.
Maintainers
High
7.5/10
Summary
Inefficient Regular Expression Complexity in chalk/ansi-regex
Affected Versions
>= 3.0.0, < 3.0.1
Patched Versions
3.0.1
High
7.5/10
Summary
Inefficient Regular Expression Complexity in chalk/ansi-regex
Affected Versions
>= 4.0.0, < 4.1.1
Patched Versions
4.1.1
High
7.5/10
Summary
Inefficient Regular Expression Complexity in chalk/ansi-regex
Affected Versions
>= 5.0.0, < 5.0.1
Patched Versions
5.0.1
High
7.5/10
Summary
Inefficient Regular Expression Complexity in chalk/ansi-regex
Affected Versions
>= 6.0.0, < 6.0.1
Patched Versions
6.0.1
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 10/30 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
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
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/chalk/ansi-regex/main.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/chalk/ansi-regex/main.yml/main?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/main.yml:21
- 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
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 10 are checked with a SAST tool
Score
4.3
/10
Last Scanned on 2025-06-23
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