Gathering detailed insights and metrics for email-regex
Gathering detailed insights and metrics for email-regex
Installations
npm install email-regexDeveloper Guide
BETA
Typescript
No
Module System
ESM
Min. Node Version
>=12
Node Version
16.0.0
NPM Version
7.10.0
Languages
2
JavaScript
TypeScript
JavaScript (92.2%)
TypeScript (7.8%)
Developer
sindresorhus
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
138 Stars
24 Commits
17 Forks
7 Watchers
1 Branches
8 Contributors
Updated on Jul 11, 2025
Sponsor this package
Maintainers
1
Package Meta Information
Latest Version
5.0.0
Package Id
email-regex@5.0.0
Size
1.81 kB
NPM Version
7.10.0
Node Version
16.0.0
Published on
May 03, 2021
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
email-regex
Regular expression for matching email addresses
Use it for finding email addresses or checking if something is email like.
You shouldn't use this for validating emails. Only for hinting to the user.
Install
$ npm install email-regex
Usage
1import emailRegex from 'email-regex'; 2 3// Contains an email address 4emailRegex().test('unicorn sindresorhus@gmail.com'); 5//=> true 6 7// Is an email address 8emailRegex({exact: true}).test('sindresorhus@gmail.com'); 9//=> true 10 11'unicorn sindresorhus@gmail.com cake john@doe.com rainbow'.match(emailRegex()); 12//=> ['sindresorhus@gmail.com', 'john@doe.com']
API
emailRegex(options?)
Returns a regex for matching email addresses.
options
Type: object
exact
Type: boolean
Default: false (Matches any email address in a string)
Only match an exact string.
Useful with RegExp#test to check if a string is an email address.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
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 5/23 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/email-regex/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/email-regex/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
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
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 5 are checked with a SAST tool
Score
3.6
/10
Last Scanned on 2025-06-30
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