npmpackage.info

Gathering detailed insights and metrics for statuses

Other packages similar to statuses

@types/statuses

2.0.6

TypeScript definitions for statuses

http-statuses

0.2.0

Http error wrapper

@bundled-es-modules/statuses

1.0.1

mirror of statuses, bundled and exposed as ES module

@zodash/statuses

1.2.8

Common HTTP status utility for node.

Gathering detailed insights and metrics for statuses

statuses - 2.0.2 | npmpackage.info

statuses

HTTP status utility

2.0.2

282

MIT

JavaScript

12.21 kB

7.6

Installations

npm install statuses

Developer Guide

BETA

Typescript

No

Module System

N/A

Min. Node Version

>= 0.8

Node Version

22.10.0

NPM Version

10.9.0 Score

99.4

Supply Chain

99.5

Quality

83.8

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

2

Total

41

Closed

10

Merged

29

Issues

Open

0

Total

11

Closed

11

Releases

v2.0.2

Updated on Jun 06, 2025

View All 1 releases

Languages

JavaScript

JavaScript (100%)

Developer

jshttp

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

282 Stars

309 Commits

28 Forks

11 Watchers

6 Branches

29 Contributors

Updated on Jul 08, 2025

Maintainers

View All 29 Contributors

Package Meta Information

Latest Version

2.0.2

Package Id

statuses@2.0.2

Unpacked Size

12.21 kB

Size

4.68 kB

File Count

NPM Version

10.9.0

Node Version

22.10.0

Published on

Jun 06, 2025

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

csv-parse eslint eslint-config-standard eslint-plugin-import eslint-plugin-markdown eslint-plugin-node eslint-plugin-promise eslint-plugin-standard mocha nyc raw-body stream-to-array

statuses

HTTP status utility for node.

This module provides a list of status codes and messages sourced from a few different projects:

Installation

This is a Node.js module available through the npm registry. Installation is done using the npm install command:

1$ npm install statuses

API

1var status = require('statuses')

status(code)

Returns the status message string for a known HTTP status code. The code may be a number or a string. An error is thrown for an unknown status code.

1status(403) // => 'Forbidden'
2status('403') // => 'Forbidden'
3status(306) // throws

status(msg)

Returns the numeric status code for a known HTTP status message. The message is case-insensitive. An error is thrown for an unknown status message.

1status('forbidden') // => 403
2status('Forbidden') // => 403
3status('foo') // throws

status.codes

Returns an array of all the status codes as Integers.

status.code[msg]

Returns the numeric status code for a known status message (in lower-case), otherwise undefined.

1status['not found'] // => 404

status.empty[code]

Returns true if a status code expects an empty body.

1status.empty[200] // => undefined
2status.empty[204] // => true
3status.empty[304] // => true

status.message[code]

Returns the string message for a known numeric status code, otherwise undefined. This object is the same format as the Node.js http module http.STATUS_CODES.

1status.message[404] // => 'Not Found'

status.redirect[code]

Returns true if a status code is a valid redirect status.

1status.redirect[200] // => undefined
2status.redirect[301] // => true

status.retry[code]

Returns true if you should retry the rest.

1status.retry[501] // => undefined
2status.retry[503] // => true

License

MIT

No vulnerabilities found.

10

Maintained

Determines if the project is "actively maintained".

10

Binary-Artifacts

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

10

Dependency-Update-Tool

Determines if the project uses a dependency update tool.

10

Dangerous-Workflow

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

10

Token-Permissions

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

10

License

Determines if the project has defined a license.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

Contributors

Determines if the project has a set of contributors from multiple organizations (e.g., companies).

9

SAST

Determines if the project uses static code analysis.

9

Security-Policy

Determines if the project has published a security policy.

7

CI-Tests

Determines if the project runs tests before pull requests are merged.

6

Code-Review

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

6

Pinned-Dependencies

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

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

Branch-Protection

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

Score

7.6

/10

Last Scanned on 2025-07-07T21:30:05Z

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