Gathering detailed insights and metrics for eslint-plugin-optimize-regex
Gathering detailed insights and metrics for eslint-plugin-optimize-regex
Installations
npm install eslint-plugin-optimize-regexDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Min. Node Version
>=10
Node Version
14.17.3
NPM Version
6.14.13
Releases
Unable to fetch releases
Languages
3
JavaScript
Makefile
Dockerfile
JavaScript (95.67%)
Makefile (2.27%)
Dockerfile (2.06%)
Developer
BrainMaestro
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
76 Stars
94 Commits
7 Forks
3 Watchers
3 Branches
7 Contributors
Updated on Feb 08, 2025
Maintainers
1
Package Meta Information
Latest Version
1.2.1
Package Id
eslint-plugin-optimize-regex@1.2.1
Size
3.91 kB
NPM Version
6.14.13
Node Version
14.17.3
Published on
Jul 26, 2021
Total Downloads
Cumulative downloads
Total Downloads
NaN
Dependencies
1
eslint-plugin-optimize-regex
Optimize regex literals
Installation
You'll first need to install ESLint:
npm i eslint --save-dev
Next, install eslint-plugin-optimize-regex:
npm install eslint-plugin-optimize-regex --save-dev
Note: If you installed ESLint globally (using the -g flag) then you must also install eslint-plugin-optimize-regex globally.
Usage
Add optimize-regex to the plugins section of your .eslintrc configuration file. You can omit the eslint-plugin- prefix:
1{ 2 "plugins": [ 3 "optimize-regex" 4 ] 5}
Then configure the rules you want to use under the rules section.
1{ 2 "rules": { 3 "optimize-regex/optimize-regex": "warn" 4 } 5}
If you wish to add a whitelist or blacklist array against regexp-tree's
transforms, you can add them on an objects object:
1{ 2 "rules": { 3 "optimize-regex/optimize-regex": ["warn", { 4 "blacklist": ["charClassClassrangesMerge"] 5 }] 6 } 7}
If you want the latter particular settings, you can avoid setting plugins and
rules and just use:
1{ 2 "extends": ["optimize-regex/recommended"] 3}
Or without the blacklist:
1{ 2 "extends": ["optimize-regex/all"] 3}
Rules
Inspiration
License
MIT © Ezinwa Okpoechi
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
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 1/5 approved changesets -- score normalized to 2
Reason
dependency not pinned by hash detected -- score normalized to 2
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.js.yml:23: update your workflow using https://app.stepsecurity.io/secureworkflow/BrainMaestro/eslint-plugin-optimize-regex/node.js.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.js.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/BrainMaestro/eslint-plugin-optimize-regex/node.js.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/npm-publish.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/BrainMaestro/eslint-plugin-optimize-regex/npm-publish.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/npm-publish.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/BrainMaestro/eslint-plugin-optimize-regex/npm-publish.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/npm-publish.yml:26: update your workflow using https://app.stepsecurity.io/secureworkflow/BrainMaestro/eslint-plugin-optimize-regex/npm-publish.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/npm-publish.yml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/BrainMaestro/eslint-plugin-optimize-regex/npm-publish.yml/master?enable=pin
- Warn: containerImage not pinned by hash: Dockerfile:1: pin your Docker image by updating node:10-alpine to node:10-alpine@sha256:dc98dac24efd4254f75976c40bce46944697a110d06ce7fa47e7268470cf2e28
- Warn: npmCommand not pinned by hash: Dockerfile:7
- Info: 0 out of 6 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 containerImage dependencies pinned
- Info: 3 out of 4 npmCommand dependencies pinned
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/node.js.yml:1
- Warn: no topLevel permission defined: .github/workflows/npm-publish.yml:1
- Info: no jobLevel write permissions found
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 28 are checked with a SAST tool
Reason
10 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-968p-4wvh-cqc8
- Warn: Project is vulnerable to: GHSA-67hx-6x53-jw92
- Warn: Project is vulnerable to: GHSA-v88g-cgmw-v5xw
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-gxpj-cx7g-858c
- Warn: Project is vulnerable to: GHSA-mwcw-c2x4-8c55
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
- Warn: Project is vulnerable to: GHSA-76p7-773f-r4q5
Score
2.8
/10
Last Scanned on 2025-07-07
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