Gathering detailed insights and metrics for regex-username
Gathering detailed insights and metrics for regex-username
Installations
npm install regex-usernameDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Node Version
6.3.0
NPM Version
3.10.3
Releases
Unable to fetch releases
Languages
2
JavaScript
Makefile
JavaScript (73.64%)
Makefile (26.36%)
Developer
regexhq
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
47 Stars
7 Commits
11 Forks
10 Watchers
2 Branches
11 Contributors
Updated on Sep 27, 2024
Maintainers
4
Package Meta Information
Latest Version
2.0.0
Package Id
regex-username@2.0.0
Size
1.85 kB
NPM Version
3.10.3
Node Version
6.3.0
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
regex-username
Regular expression for usernames - it follows the same rules that GitHub uses.
Installation
1npm install regex-username
Usage
1var regex = require('regex-username'); 2 3regex().test('foo-bar'); // => true 4regex().test('foobar'); // => true 5regex().test('3foobar'); // => true 6regex().test('3foo-bar'); // => true 7regex().test('foo-bar-'); // => false 8regex().test('-foo-bar'); // => false 9regex().test('foo--bar'); // => false 10regex().test('~derp@darp---++asdf'); // => false 11regex().test('derp@mail.com'); // => false
Why?
Which usernames to allow typically varies between applications. For prototypes however it's nice to have an off the shelf solution. This module is that solution. It follows the same rules GitHub uses:
Username may only contain alphanumeric characters or single hyphens, and cannot begin or end with a hyphen.
See Also
License
No vulnerabilities found.
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 2/7 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
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 2 are checked with a SAST tool
Score
3.3
/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