Gathering detailed insights and metrics for http-status-identifier-cli
Gathering detailed insights and metrics for http-status-identifier-cli
🔍 What's my HTTP status...without leaving the command line
Installations
npm install http-status-identifier-cliDeveloper Guide
BETA
Typescript
No
Module System
N/A
Node Version
12.14.1
NPM Version
6.14.4
Releases
7
Languages
1
JavaScript
JavaScript (100%)
Developer
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
23 Stars
145 Commits
2 Forks
2 Watchers
29 Branches
3 Contributors
Updated on Nov 03, 2023
Maintainers
1
Package Meta Information
Latest Version
1.1.6
Package Id
http-status-identifier-cli@1.1.6
Unpacked Size
11.67 kB
Size
4.32 kB
File Count
10
NPM Version
6.14.4
Node Version
12.14.1
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
Dev Dependencies
21
HTTP Status Identifier CLI
- Purpose
- Installation
- Usage
- Examples
- Get the HTTP Status for HTTP Status Code
200 - Get the HTTP Status for HTTP Status Name
I'm a teapot - Get the HTTP Status with additional information
- Get the HTTP Statuses for HTTP Status Codes
100,200,300,400, and500 - Get the HTTP Statuses for a combination of HTTP Status Codes (
100,200) and HTTP Status Names (I'm a teapot,Bad Request) - Get the HTTP Status for
200and open the documentation page in the default browser
- Get the HTTP Status for HTTP Status Code
- Examples
Purpose
A command line interface to identify HTTP statuses from status codes (i.e. 200) or status names (i.e. I'm a teapot).
Installation
Install via NPM (the -g flag will install the package globally):
1npm install http-status-identifier-cli -g
Usage
The command to identify HTTP statuses is hs.
It expects a list of HTTP status codes or HTTP status names. It will return a table containing the HTTP status names, HTTP status codes, and the meaning of the specified HTTP statuses.
If the -f (or --fullDescription) flag is included, an additional supplementary information field is included that provides even more information into the HTTP status. Sometimes, this field is empty if there is no additional information.
If the -d of (--documentation) flag is included, your default browser will open the documentation pages for each of the specified HTTP statuses.
The -h (or --help) flag is useful if you ever need help.
Examples
Get the HTTP Status for HTTP Status Code 200
1hs 200
Get the HTTP Status for HTTP Status Name I'm a teapot
1hs "I'm a teapot"
Get the HTTP Status with additional information
1hs 200 -f
Get the HTTP Statuses for HTTP Status Codes 100, 200, 300, 400, and 500
1hs 100 200 300 400 500
Get the HTTP Statuses for a combination of HTTP Status Codes (100, 200) and HTTP Status Names (I'm a teapot, Bad Request)
1hs 100 "I'm a teapot" 200 "Bad request"
Get the HTTP Status for 200 and open the documentation page in the default browser
1hs 200 -d
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 5/9 approved changesets -- score normalized to 5
Reason
dependency not pinned by hash detected -- score normalized to 5
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/workflows.yaml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/jaebradley/http-status-identifier-cli/workflows.yaml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/workflows.yaml:26: update your workflow using https://app.stepsecurity.io/secureworkflow/jaebradley/http-status-identifier-cli/workflows.yaml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/workflows.yaml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/jaebradley/http-status-identifier-cli/workflows.yaml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/workflows.yaml:50: update your workflow using https://app.stepsecurity.io/secureworkflow/jaebradley/http-status-identifier-cli/workflows.yaml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/workflows.yaml:54: update your workflow using https://app.stepsecurity.io/secureworkflow/jaebradley/http-status-identifier-cli/workflows.yaml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/workflows.yaml:60: update your workflow using https://app.stepsecurity.io/secureworkflow/jaebradley/http-status-identifier-cli/workflows.yaml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/workflows.yaml:67: update your workflow using https://app.stepsecurity.io/secureworkflow/jaebradley/http-status-identifier-cli/workflows.yaml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/workflows.yaml:71: update your workflow using https://app.stepsecurity.io/secureworkflow/jaebradley/http-status-identifier-cli/workflows.yaml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/workflows.yaml:77: update your workflow using https://app.stepsecurity.io/secureworkflow/jaebradley/http-status-identifier-cli/workflows.yaml/master?enable=pin
- Info: 0 out of 7 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 2 third-party GitHubAction dependencies pinned
- Info: 3 out of 3 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/workflows.yaml: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 30 are checked with a SAST tool
Reason
67 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-h5c3-5r3r-rr8q
- Warn: Project is vulnerable to: GHSA-rmvr-2pp2-xj38
- Warn: Project is vulnerable to: GHSA-xx4v-prfh-6cgc
- Warn: Project is vulnerable to: GHSA-6chw-6frg-f759
- Warn: Project is vulnerable to: GHSA-v88g-cgmw-v5xw
- Warn: Project is vulnerable to: GHSA-93q8-gq69-wqmw
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-w8qv-6jwh-64r5
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-gxpj-cx7g-858c
- Warn: Project is vulnerable to: GHSA-w573-4hg7-7wgq
- Warn: Project is vulnerable to: GHSA-ff7x-qrg7-qggm
- Warn: Project is vulnerable to: GHSA-ww39-953v-wcq6
- Warn: Project is vulnerable to: GHSA-pfrx-2q88-qq97
- Warn: Project is vulnerable to: GHSA-765h-qjxv-5f44
- Warn: Project is vulnerable to: GHSA-f2jv-r9rf-7988
- Warn: Project is vulnerable to: GHSA-43f8-2h32-f4cj
- Warn: Project is vulnerable to: GHSA-rc47-6667-2j5j
- Warn: Project is vulnerable to: GHSA-78xj-cgh5-2h22
- Warn: Project is vulnerable to: GHSA-2p57-rm9w-gvfp
- Warn: Project is vulnerable to: GHSA-896r-f27r-55mw
- Warn: Project is vulnerable to: GHSA-9c47-m6qq-7p4h
- Warn: Project is vulnerable to: GHSA-jf85-cpcp-j695
- Warn: Project is vulnerable to: GHSA-fvqr-27wr-82fm
- Warn: Project is vulnerable to: GHSA-4xc9-xhrj-v574
- Warn: Project is vulnerable to: GHSA-x5rq-j2xg-h7qm
- Warn: Project is vulnerable to: GHSA-p6mc-m468-83gw
- Warn: Project is vulnerable to: GHSA-29mw-wpgm-hmr9
- Warn: Project is vulnerable to: GHSA-35jh-r3h4-6jhm
- Warn: Project is vulnerable to: GHSA-4r62-v4vq-hr96
- Warn: Project is vulnerable to: GHSA-5v2h-r2cx-5xgj
- Warn: Project is vulnerable to: GHSA-rrrm-qjm4-v8hf
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
- Warn: Project is vulnerable to: GHSA-f8q6-p94x-37v3
- Warn: Project is vulnerable to: GHSA-vh95-rmgr-6w4m
- Warn: Project is vulnerable to: GHSA-xvch-5gv4-984h
- Warn: Project is vulnerable to: GHSA-r683-j2x4-v87g
- Warn: Project is vulnerable to: GHSA-5fw9-fq32-wv5p
- Warn: Project is vulnerable to: GHSA-px4h-xg32-q955
- Warn: Project is vulnerable to: GHSA-pw54-mh39-w3hc
- Warn: Project is vulnerable to: GHSA-xgh6-85xh-479p
- Warn: Project is vulnerable to: GHSA-hj48-42vr-x3v9
- Warn: Project is vulnerable to: GHSA-hrpp-h998-j3pp
- Warn: Project is vulnerable to: GHSA-p8p7-x288-28g6
- Warn: Project is vulnerable to: GHSA-x2pg-mjhr-2m5x
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
- Warn: Project is vulnerable to: GHSA-44c6-4v22-4mhx
- Warn: Project is vulnerable to: GHSA-4x5v-gmq8-25ch
- Warn: Project is vulnerable to: GHSA-wpg7-2c88-r8xv
- Warn: Project is vulnerable to: GHSA-vx3p-948g-6vhq
- Warn: Project is vulnerable to: GHSA-3jfq-g458-7qm9
- Warn: Project is vulnerable to: GHSA-r628-mhmh-qjhw
- Warn: Project is vulnerable to: GHSA-9r2w-394v-53qc
- Warn: Project is vulnerable to: GHSA-5955-9wpr-37jh
- Warn: Project is vulnerable to: GHSA-qq89-hq3f-393p
- Warn: Project is vulnerable to: GHSA-f5x3-32g6-xq36
- Warn: Project is vulnerable to: GHSA-jgrx-mgxx-jf9v
- Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3
- Warn: Project is vulnerable to: GHSA-7p7h-4mm5-852v
- Warn: Project is vulnerable to: GHSA-38fc-wpqx-33j7
- Warn: Project is vulnerable to: GHSA-j8xg-fqg3-53r7
- Warn: Project is vulnerable to: GHSA-6fc8-4gx4-v693
- Warn: Project is vulnerable to: GHSA-3h5v-q93c-6h6q
- Warn: Project is vulnerable to: GHSA-p9pc-299p-vxgp
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