Gathering detailed insights and metrics for requires-port
Gathering detailed insights and metrics for requires-port
Gathering detailed insights and metrics for requires-port
Gathering detailed insights and metrics for requires-port
Check if a protocol requires a certain port number to be added to an URL.
npm install requires-port
99.9
Supply Chain
80.2
Quality
77.5
Maintenance
100
Vulnerability
100
License
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
11 Stars
52 Commits
5 Forks
5 Watching
1 Branches
4 Contributors
Updated on 23 Mar 2024
Minified
Minified + Gzipped
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
-21.7%
4,309,676
Compared to previous day
Last week
-4.6%
28,239,153
Compared to previous week
Last month
2.6%
121,738,935
Compared to previous month
Last year
20.4%
1,296,917,276
Compared to previous year
4
The module name says it all, check if a protocol requires a given port.
This module is intended to be used with browserify or Node.js and is distributed in the public npm registry. To install it simply run the following command from your CLI:
npm install --save requires-port
The module exports it self as function and requires 2 arguments:
http
, http:
or even https://yomoma.com
. We just split
it at :
and use the first result. We currently accept the following
protocols:
http
https
ws
wss
ftp
gopher
file
It returns a boolean that indicates if protocol requires this port to be added to your URL.
1'use strict'; 2 3var required = require('requires-port'); 4 5console.log(required('8080', 'http')) // true 6console.log(required('80', 'http')) // false
MIT
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
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
Found 0/17 approved changesets -- score normalized to 0
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
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2024-11-18
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