npmpackage.info

Gathering detailed insights and metrics for pragmatic-email-regex

Other packages similar to pragmatic-email-regex

@atlaskit/pragmatic-drag-and-drop

1.4.0

The core package for Pragmatic drag and drop - enabling fast drag and drop for any experience on any tech stack

emoji-regex

10.4.0

A regular expression to match all Emoji-only symbols as per the Unicode Standard.

url-regex-safe

4.0.0

Regular expression matching for URL's. Maintained, safe, and browser-friendly version of url-regex. Resolves CVE-2020-7661. Works in Node v10.12.0+ and browsers.

@atlaskit/pragmatic-drag-and-drop-hitbox

1.0.3

An optional package for Pragmatic drag and drop that enables the attaching of interaction information to a drop target

Gathering detailed insights and metrics for pragmatic-email-regex

pragmatic-email-regex

1.0.4

TypeScript

14,124 2.2

Installations

npm install pragmatic-email-regex

Score

68.6

Supply Chain

Quality

75.4

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

0

Total

0

Closed

0

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Developer

MaxEvan

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

No

Node Version

14.18.0

NPM Version

6.14.15 Statistics

11 Commits

2 Watching

1 Branches

1 Contributors

Updated on 30 Sept 2021

Languages

TypeScript (87.54%)

JavaScript (9.27%)

Shell (3.19%)

Total Downloads

Cumulative downloads

Total Downloads

14,124

Last day

400%

Compared to previous day

Last week

66.7%

Compared to previous week

Last month

-38.6%

Compared to previous month

Last year

-45%

1,009

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

@types/jest jest pre-commit ts-jest typescript

Versions

pragmatic-email-regex

Disclaimer

I am not a specialist when it comes to this subject. Just a pragmatic programmer who wants to help.

Why ?

After building a whole lot of different web applications, I often came across cases where users enter all kinds of weird email addresses in my forms, sometimes even using discount coupons thinking that's what they had to do. This library is by no means a perfect source of truth when it comes to email validation, and it's not trying to be. People who want to nitpick about the exact specs and all the gazillion theoretical possibilities of the correct email string format are gonna be right when they say my library is not perfect. I'm not saying it is, I'm just sayin it's a solid, pragmatic, effective way to filter out most of the cases and hint users about their weird ass looking emails before they submit something that is not going to work either by mistake or simply to be annoying.

Plus it gave me a small pet project to test out github actions to automatically publish an npm package when pushing or merging to master...

How ?

I built this regular expression from inspirations on the web and by cross-checking with some of the big tech websites to see if it made sense when trying to filter out weird email addresses.

Installation

1$ yarn add pragmatic-email-regex

1$ npm i pragmatic-email-regex

Usage

1// I recommend importing it with that name cause it makes more sense in the code.
2import isValidEmail from 'pragmatic-email-regex';
3
4// Return value is true or false depending on the string shape, that's it.
5isValidEmail('email@right.here'); // true

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

SAST

Determines if the project uses static code analysis.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Fuzzing

Determines if the project uses fuzzing.

0

Security-Policy

Determines if the project has published a security policy.

0

License

Determines if the project has defined a license.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

2.2

/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